python/jc
1
0
Fork 0
mirror of https://github.com/kellyjonbrazil/jc.git synced 2025-07-13 01:20:24 +02:00
Code Issues Releases Activity

formatting

Browse Source
This commit is contained in:
Kelly Brazil
2022-03-09 14:43:56 -08:00
parent c3198a5874
commit f5c7d52ec7
2 changed files with 2 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
man/jc.1
View File

@ -568,7 +568,6 @@ You may want to ignore parsing errors when using streaming parsers since these m
.RS
Successfully parsed line with \fB-qq\fP option:
.RS
.na
.nf
{
"command_data": "data",
@ -576,11 +575,11 @@ Successfully parsed line with \fB-qq\fP option:
"success": true
}
}
.fi
.RE
Unsuccessfully parsed line with \fB-qq\fP option:
.RS
.na
.nf
{
"_jc_meta": {
@ -598,7 +597,6 @@ Unsuccessfully parsed line with \fB-qq\fP option:
Most operating systems will buffer output that is being piped from process to process. The buffer is usually around 4KB. When viewing the output in the terminal the OS buffer is not engaged so output is immediately displayed on the screen. When piping multiple processes together, though, it may seem as if the output is hanging when the input data is very slow (e.g. \fBping\fP):
.RS
.na
.nf
$ ping 1.1.1.1 | jc \fB--ping-s\fP | jq
<slow output>
@ -608,7 +606,6 @@ $ ping 1.1.1.1 | jc \fB--ping-s\fP | jq
This is because the OS engages the 4KB buffer between \fBjc\fP and \fBjq\fP in this example. To display the data on the terminal in realtime, you can disable the buffer with the \fB-u\fP (unbuffer) cli option:
.RS
.na
.nf
$ ping 1.1.1.1 | jc \fB--ping-s\fP \fB-u\fP | jq
{"type":"reply","pattern":null,"timestamp":null,"bytes":"64",...}
@ -623,7 +620,6 @@ Note: Unbuffered output can be slower for large data streams.
Custom local parser plugins may be placed in a \fBjc/jcparsers\fP folder in your local "App data directory":
.RS
.na
.nf
- Linux/unix: \fB$HOME/.local/share/jc/jcparsers\fP
- macOS: \fB$HOME/Library/Application Support/jc/jcparsers\fP

6
templates/manpage_template
View File

@ -123,7 +123,6 @@ You may want to ignore parsing errors when using streaming parsers since these m
.RS
Successfully parsed line with \fB-qq\fP option:
.RS
.na
.nf
{
"command_data": "data",
@ -131,11 +130,11 @@ Successfully parsed line with \fB-qq\fP option:
"success": true
}
}
.fi
.RE
Unsuccessfully parsed line with \fB-qq\fP option:
.RS
.na
.nf
{
"_jc_meta": {
@ -153,7 +152,6 @@ Unsuccessfully parsed line with \fB-qq\fP option:
Most operating systems will buffer output that is being piped from process to process. The buffer is usually around 4KB. When viewing the output in the terminal the OS buffer is not engaged so output is immediately displayed on the screen. When piping multiple processes together, though, it may seem as if the output is hanging when the input data is very slow (e.g. \fBping\fP):
.RS
.na
.nf
$ ping 1.1.1.1 | jc \fB--ping-s\fP | jq
<slow output>
@ -163,7 +161,6 @@ $ ping 1.1.1.1 | jc \fB--ping-s\fP | jq
This is because the OS engages the 4KB buffer between \fBjc\fP and \fBjq\fP in this example. To display the data on the terminal in realtime, you can disable the buffer with the \fB-u\fP (unbuffer) cli option:
.RS
.na
.nf
$ ping 1.1.1.1 | jc \fB--ping-s\fP \fB-u\fP | jq
{"type":"reply","pattern":null,"timestamp":null,"bytes":"64",...}
@ -178,7 +175,6 @@ Note: Unbuffered output can be slower for large data streams.
Custom local parser plugins may be placed in a \fBjc/jcparsers\fP folder in your local "App data directory":
.RS
.na
.nf
- Linux/unix: \fB$HOME/.local/share/jc/jcparsers\fP
- macOS: \fB$HOME/Library/Application Support/jc/jcparsers\fP