You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Second scenario is even more interesting.
Unzip attached file test.gz
( cat /tmp/test; sleep 10000 ) | less -SBnb100
Enter: /asbcuBfDxkOwf379kKqCyg6UidFq
Press: nn
You will see: Cannot seek to that file position (press RETURN)
Press: Ctrl-C
Press: UP arrow
At this point program will be stopped and moved into background.
To kill it, you need to do fg, Ctrl-C, q[ENTER]
If you press "q" after Ctrl-C (instead of UP arrow), the program will be stopped and goes into the background as well. But after fg it will immediately quit. This means that the 'q' input was somehow buffered.
I see some glitches when using buffer (-B) with search and piped stream
First test scenario:
perl -e 'for (my $i=0; ; $i++) { print($i.("x"x100)."\n"); print "$i test\n" if ($i<400 and !($i%100)); }' | less -nBb1
Notice that program is still running in background, but less is stuck without progress
The text was updated successfully, but these errors were encountered: