I just read on stackoverflow about a feature I didn't know yet:
https://unix.stackexchange.com/questions/417052/with-bash-after-scrolling-up-to-a-previous-command-how-to-then-move-on-to-t
If you're editing history commands, you can type Control-O to run the
command and go on to the next one. Very convenient. Except for me it
doesn't work.
The feature is mentioned in our bash manual:
READLINE
...
Commands for Manipulating the History
...
operate-and-get-next (C-o)
Accept the current line for execution and fetch the next line
relative to the current line from the history for editing. Any
argument is ignored.
I made a guess that perhaps bash doesn't see C-o because it is the
disard character:
$ stty -a
speed 38400 baud; 66 rows; 80 columns; queue = 1024; line = termios;
lflags: icanon isig iexten echo echoe echok echoke -echonl echoctl
-echoprt -altwerase -noflsh -tostop -flusho pendin -nokerninfo
-extproc
iflags: -istrip icrnl -inlcr -igncr ixon -ixoff -ixany imaxbel -ignbrk
brkint -inpck ignpar -parmrk
oflags: opost onlcr -ocrnl -oxtabs -onocr -onlret
cflags: cread cs8 -parenb -parodd hupcl -clocal -cstopb -crtscts -mdmbuf
-cdtrcts
cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = <undef>; eol2 = ^@;
erase = ^H; intr = ^C; kill = ^U; lnext = ^V; min = 1; quit = ^\;
reprint = ^R; start = ^Q; status = ^T; stop = ^S; susp = ^Z;
time = 0; werase = ^W;
but on the other hand, I thought bash doesn't run the terminal in cooked
mode especially because of special control characters.
So what's going on here?
-Olaf.
--
___ Olaf 'Rhialto' Seibert -- Wayland: Those who don't understand X
\X/ rhialto/at/falu.nl -- are condemned to reinvent it. Poorly.
Attachment:
signature.asc
Description: PGP signature