From: Lars Ingebrigtsen <larsi@gnus.org>
To: Hadrien Lacour <hadrien.lacour@posteo.net>
Cc: 33513@debbugs.gnu.org
Subject: bug#33513: 26.1; emacsclient forgetting keybinds set by tty-setup-hook
Date: Fri, 27 Nov 2020 09:41:37 +0100 [thread overview]
Message-ID: <87k0u7jiny.fsf@gnus.org> (raw)
In-Reply-To: <20201126153249.3kxdhmwrx5vy7vaq@gentoo-zen2700x> (Hadrien Lacour's message of "Thu, 26 Nov 2020 16:32:49 +0100")
Hadrien Lacour <hadrien.lacour@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.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-11-27 8:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 10:51 bug#33513: 26.1; emacsclient forgetting keybinds set by tty-setup-hook Hadrien Lacour
2020-11-26 12:22 ` Lars Ingebrigtsen
2020-11-26 15:32 ` Hadrien Lacour
2020-11-27 8:41 ` Lars Ingebrigtsen [this message]
2020-11-28 9:12 ` Hadrien Lacour
2020-11-28 9:23 ` Eli Zaretskii
2022-01-29 15:24 ` Lars Ingebrigtsen
2022-01-30 9:44 ` Hadrien Lacour
2022-01-30 16:02 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k0u7jiny.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=33513@debbugs.gnu.org \
--cc=hadrien.lacour@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).