fish: arrows and backspace keys no longer supported after 11.0-RELEASE upgrade
david.guyot at europecamions-interactive.com
Thu Oct 20 07:49:25 UTC 2016
On mer., 2016-10-19 at 18:30 +0200, Polytropon wrote:
> On Wed, 19 Oct 2016 13:51:42 +0200, David Guyot wrote:
> > Hello, there.
> > I was using a 10.3-RELEASE FreeBSD with the packaged fish 2.2.0
> > installed, without customization, and upgraded my system and
> > packages
> > to 11.0-RELEASE. fish were upgraded to 2.3.1, and I lost the
> > previous
> > default prompt, but that doesn't really matter. My main problem is
> > that
> > it lost support of arrows and backspace keys: whenever I try to use
> > them, I get this:
> > # Up arrow for autocompletion with the last command
> > penegal at Aethelthryth-FreeBSD~/usr/home/penegal> [A
> > # Right arrow for autocompletion with the last similar command,
> > then
> > # left arrow to correct input
> > penegal at Aethelthryth-FreeBSD~/usr/home/penegal> ls[C[D
> What you see there is the escape code sequence of those
> keys, without the actual escape happening.
> The code ^[[A (read: ^[ = escape, [ = left bracket, A)
> is the cursor up key; ^[[C and ^[[D are right and left
> There has been a regression recently regarding sh not
> interpreting escape characters anymore, caused by libedit:
> It could be possible that you're seeing something related
> to the same origin.
Well, that seems related, but I can't be sure of it, as I'm not
accustomed to such a technical level. I tested arrows with /bin/sh as a
shell, but it correctly processed the inputs.
> What does
> $ stty -a
> show for those control character?
I'm not sure of what I'm looking for, so here comes the full output:
penegal at Aethelthryth-FreeBSD~/usr/home/penegal> stty -a
speed 9600 baud; 69 rows; 272 columns;
lflags: icanon isig iexten echo echoe -echok echoke -echonl echoctl
-echoprt -altwerase -noflsh -tostop -flusho -pendin -nokerninfo
iflags: -istrip icrnl -inlcr -igncr -ixon -ixoff ixany imaxbel -ignbrk
brkint -inpck -ignpar -parmrk
oflags: opost onlcr -ocrnl tab0 -onocr -onlret
cflags: cread cs8 -parenb -parodd hupcl -clocal -cstopb -crtscts
cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = <undef>;
eol2 = <undef>; erase = ^?; erase2 = ^H; intr = ^C; kill = ^U;
lnext = ^V; min = 1; quit = ^\; reprint = ^R; start = ^Q;
status = ^T; stop = ^S; susp = ^Z; time = 0; werase = ^W;
> > I suspect a configuration that broke upon the upgrade, but am
> > unsure
> > about it, and the fish changelog doen't seem to have anything
> > related,
> > but I'm not accustomed to its internals and can have missed it.
> > Does
> > somebody have suggestions?
> Read the bug report mentioned above. Does this sound reasonable?
> Maybe you should also file a bug report or add something to the
> existing one.
I'll report my problem on this bug report; if I'm told it's unrelated,
then I'll assume this is a new bug. In the case this is a different
bug, should I contact the package mainainer, or open a FreeBSD bug?
(Newbie question, but I'm a newbie, so I prefer to ask.)
Thank you, Polytropon.
P.-S. : also, thanks, James Keenan.
Administrateur système, réseau et télécom / Sysadmin
Europe Camions Interactive / Stockway
03 29 30 47 85
More information about the freebsd-questions