Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 19 Oct 2016 12:43:44 -0400
From:      James E Keenan <jkeen@verizon.net>
To:        freebsd-questions@freebsd.org
Subject:   =?UTF-8?Q?Re:_fish:_arrows_and_backspace_keys_no_longer_supported_a?= =?UTF-8?Q?fter_11.0-RELEASE=c2=a0upgrade?=
Message-ID:  <81cdbd80-3c5a-a1fe-8c93-74ae4c270e78@verizon.net>
In-Reply-To: <1476877902.1196.27.camel@europecamions-interactive.com>
References:  <1476877902.1196.27.camel@europecamions-interactive.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 10/19/2016 07:51 AM, 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@Aethelthryth-FreeBSD~/usr/home/penegal> [A
> # Right arrow for autocompletion with the last similar command, then
> # left arrow to correct input
> penegal@Aethelthryth-FreeBSD~/usr/home/penegal> ls[C[D
>
> Tab still functions as usual; backspace produces no result, so I have
> to Ctrl+C to erase the line and restart the typing from the start. As I
> also use fish as the root shell, the problem persists when using sudo
> su, but not with su -; the problem is also present when using fish from
> vt, and the su tweak works all the same. bash doesn't have this problem
> and responds as usual to these keys, as do fish over SSH connections,
> so it's not keyboard-related.
>
> 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?
>
> Awaiting your answers,
>
> Regards.
>

Could it be the problem described in 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211360 and discussed 
in the thread with 'PS1' in the subject line on this list during the 
past two weeks?




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?81cdbd80-3c5a-a1fe-8c93-74ae4c270e78>