Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add support for piping input to CodeEdit via CLI

Open
#34 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
swift
Domain
cli

Research direction

Start by locating the codeedit CLI entry point and its existing argument and file-opening handling. Reproduce the documented echo pipeline, then define how piped input is detected, represented as a temporary file, opened in CodeEdit, and cleaned up after editing; done means the example workflow works without disrupting normal file and folder arguments.

Written by the indexing model from the issue text.

Description

The codeedit CLI currently does not support receiving input via pipe (|). Introducing this feature would allow developers to seamlessly use the codeedit CLI to interact with the CodeEdit app, enabling workflows similar to those supported by other editors, such as Sublime Text's subl CLI, which supports piping input directly into the editor.

Use Case

Developers often use CLI tools to process text and may want to quickly edit the output in CodeEdit. For example:

echo "Sample text" | codeedit  

With this feature, the codeedit CLI would behave similarly to subl from Sublime Text, opening a new tab or window in CodeEdit with the piped content for editing.

Benefits
  • Expands the utility of the codeedit CLI in developer workflows.
  • Positions CodeEdit as a competitive choice alongside editors like Sublime Text.
  • Enables seamless integration with terminal-based pipelines.
Suggested Implementation
  1. Input Detection:
    The codeedit CLI should recognize when input is piped into it.

  2. Temporary File Handling:
    Create a temporary file containing the piped input and open it in CodeEdit.

  3. Optional Flag:
    Provide a --pipe flag to explicitly handle piped input, similar to how subl operates.

Example
# Open piped text in CodeEdit  
echo "Edit this text" | codeedit  

# Example from Sublime Text for comparison  
echo "Edit this text" | subl  
Additional Considerations
  • Temporary File Management: Ensure that temporary files are removed after the editing session ends.
  • Efficient Input Handling: Handle large piped inputs efficiently to avoid performance bottlenecks.
  • Custom Options: Allow configuring how piped input is managed (e.g., open in a new tab, new window, or append to an existing file).

By adopting a similar approach as subl, CodeEdit could provide a familiar and powerful experience for developers, while leveraging CodeEdit's unique features and interface.

Dominant language
Swift
Stars
81
Forks
19
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CodeEditApp/CodeEditCLI

All issues in CodeEditApp/CodeEditCLI

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.