brothyPipes & editor
Read Markdown from a pipe with brothy -, and open the note in your editor with e.
Reading a pipe
Section titled “Reading a pipe”curl -s … | brothy or brothy - < note.md shows the piped text as a single document titled stdin (up to 5 MB; more stops with brothy: input too large (limit 5 MB)). Keys are read from /dev/tty, so stdout and a controlling terminal are still required.
What changes for a pipe:
- There is no Files tab (1 Outline, 2 Info), no live reload and no recent-project entry.
asummarizes for this run only (never cached, glosses too).[[links]]resolve against the notes under the current folder, which is scanned in the background right after start (a link used sooner scans at once; until then every link looks unresolved).
Editing
Section titled “Editing”e opens the note in $VISUAL, else $EDITOR (fallback vi), at the line at the top of the view: exact in Source, from the nearest heading in Preview. VS Code, VSCodium and Cursor get -g path:line and Sublime Text path:line; everything else gets +line path. brothy resumes and reloads when the editor exits, and says so when it exits with an error.
On a piped document there is nothing to edit (e says so). On a note followed from piped input the editor reads its keys from /dev/tty too.
brothy is a reader for a folder of notes, not an editor: this is the only other program it ever runs.