mirror of
https://github.com/jrnl-org/jrnl.git
synced 2025-05-10 08:38:32 +02:00
Add note about messages going to stderr
and the implication for piping (#1768)
* Add note about messages going to STDERR and the implication for piping * Minor wording change * Wording and capitalization changes
This commit is contained in:
parent
7a9bc929a5
commit
c6b9114c42
1 changed files with 5 additions and 0 deletions
|
@ -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
|
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).
|
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
|
### JSON
|
||||||
|
|
||||||
``` sh
|
``` sh
|
||||||
|
|
Loading…
Add table
Reference in a new issue