GNU bug report logs - #33513
26.1; emacsclient forgetting keybinds set by tty-setup-hook

Previous Next

Full log

View this message in rfc822 format

From: Hadrien Lacour <hadrien.lacour <at> posteo.net>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 33513 <at> debbugs.gnu.org
Subject: bug#33513: 26.1; emacsclient forgetting keybinds set by tty-setup-hook
Date: Sat, 28 Nov 2020 10:12:58 +0100

On Fri, Nov 27, 2020 at 09:41:37AM +0100, Lars Ingebrigtsen wrote:
> Hadrien Lacour <hadrien.lacour <at> posteo.net> writes:
>
> >> > (define-key input-decode-map "^[[1;5A" [C-up])
> >>
> >> [...]
> >>
> >> > I get the keybinds I want when using emacs -nw with st, but when using
> >> > emacs --daemon and emacsclient, these work only the first time:
> >> > $ emacs --daemon
> >> > $ emacsclient -nw myfile # no problem, close with C-x C-c
> >> > $ emacsclient -nw myfile # from here, tty frames don't remember the bindings
> >>
> >> (This bug report unfortunately got no response at the time.)
> >>
> >> What key stroke is "^[[1;5A" (etc) representing?
>
> [...]
>
> > as the line says, "Ctrl + Up arrow". I think I stopped used
> > emacsclient because of this, actually.
>
> When I use emacsclient -nw (Debian bullseye), `C-up' works without
> altering input-decode-map, so I'm wondering why your terminal is sending
> key sequences making it necessary to alter input-decode-map.

Most probably because Emacs has some defaults for xterm based terminals, which
st isn't. And Emacs needs those defaults because "C-up" isn't described by
terminfo.

Anyway, that's not really the problem, the bindings shouldn't
disappear. Mind you, I haven't try to reproduce it with the current version,
I'll probably get to it.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.