michael/lf
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

update doc

Browse Source
This commit is contained in:
Gokcehan 2020-12-19 17:25:44 +03:00
parent fd688c675b
commit ed5104cfdb
3 changed files with 3 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc.go
View File

@ -912,7 +912,7 @@ For example, an alternative rename command may look like this:
cmd rename %[ -e $1 ] && printf "file exists" || mv $f $1
One thing to be careful is that although input is still line buffered, output and error are byte buffered and verbose commands will be very slow to display.
Note that input is line buffered and output and error are byte buffered.
Waiting Shell Commands

4
docstring.go
View File

@ -996,9 +996,7 @@ statline. For example, an alternative rename command may look like this:
cmd rename %[ -e $1 ] && printf "file exists" || mv $f $1
One thing to be careful is that although input is still line buffered,
output and error are byte buffered and verbose commands will be very slow to
display.
Note that input is line buffered and output and error are byte buffered.
Waiting Shell Commands

2
lf.1
View File

@ -1080,7 +1080,7 @@ You can also output error messages in the command and it will show up in the sta
cmd rename %[ -e $1 ] && printf "file exists" || mv $f $1
.EE
.PP
One thing to be careful is that although input is still line buffered, output and error are byte buffered and verbose commands will be very slow to display.
Note that input is line buffered and output and error are byte buffered.
.SH WAITING SHELL COMMANDS
Waiting shell commands are similar to regular shell commands except that they wait for a key press when the command is finished. These can be useful to see the output of a program before the ui is resumed. Waiting shell commands are more appropriate than piping shell commands when the command is verbose and the output is best displayed as multiline.
.SH ASYNCHRONOUS SHELL COMMANDS