Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add note about messages going to stderr and the implication for piping #1768

Merged
merged 3 commits into from Jul 15, 2023
Merged

Add note about messages going to stderr and the implication for piping #1768

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e689aeb
Add note about messages going to STDERR and the implication for piping
micahellison Jul 10, 2023
e88749a
Minor wording change
micahellison Jul 10, 2023
759c7ca
Wording and capitalization changes
micahellison Jul 10, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/formats.md
View file
Open in desktop
Expand Up @@ -117,6 +117,11 @@ These formats are mainly intended for piping or exporting your journal to other
programs. Even so, they can still be used in the same way as any other format (like
written to a file, or displayed in your terminal, if you want).

!!! note
You may see boxed messages like "2 entries found" when using these formats, but
those messages are written to `stderr` instead of `stdout`, and won't be piped when
using the `|` operator.

### JSON

``` sh
Expand Down