all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Hadrien Lacour <hadrien.lacour@posteo.net>
Cc: larsi@gnus.org, 33513@debbugs.gnu.org
Subject: bug#33513: 26.1; emacsclient forgetting keybinds set by tty-setup-hook
Date: Sat, 28 Nov 2020 11:23:11 +0200	[thread overview]
Message-ID: <83sg8tn8cg.fsf@gnu.org> (raw)
In-Reply-To: <20201128091258.v5f2nnj7ntba4cqu@gentoo-zen2700x> (message from Hadrien Lacour on Sat, 28 Nov 2020 10:12:58 +0100)

> Date: Sat, 28 Nov 2020 10:12:58 +0100
> From: Hadrien Lacour <hadrien.lacour@posteo.net>
> Cc: 33513@debbugs.gnu.org
> 
> > >> 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.

So maybe the way forward is to update lisp/term/st.el with these
sequences?  Currently, we behave as if st is the same as xterm.

> 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.

Please do, perhaps the latest code already fixes this problem.

Thanks.





  reply	other threads:[~2020-11-28  9:23 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
2020-11-28  9:12       ` Hadrien Lacour
2020-11-28  9:23         ` Eli Zaretskii [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83sg8tn8cg.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=33513@debbugs.gnu.org \
    --cc=hadrien.lacour@posteo.net \
    --cc=larsi@gnus.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.