unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Yuri Khan <yuri.v.khan@gmail.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: Luca Ferrari <fluca1978@gmail.com>,
	help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: . is undefined (when pressing C-.): is ssh behaving odd?
Date: Tue, 7 Dec 2021 01:02:19 +0700	[thread overview]
Message-ID: <CAP_d_8VyHR0RJnm7-VEfvnXi1m1+_Vg4UierVC6_o37oe8a92g@mail.gmail.com> (raw)
In-Reply-To: <87mtldhchk.fsf@gmail.com>

On Tue, 7 Dec 2021 at 00:25, Robert Pluim <rpluim@gmail.com> wrote:

>>> tty's canʼt produce 'C-.'

This is technically correct if one limits oneself to a hardware
terminal made half a century ago, or even to a Linux TTY.

> There are limitations to the keys that can be produced when using a
> tty (such as when youʼre logged in over ssh, or running 'emacs
> -nw'). One of those is that certain Ctrl combinations simply won't
> work: C-. is one of them.  There is no fix: itʼs an inherent
> limitation of the tty technology.

The fix is to use a terminal emulator that implements extended key
codes, to opt in to such a protocol extension, and to teach Emacs to
decode that.

Here’s one such extension.
https://sw.kovidgoyal.net/kitty/keyboard-protocol/

(No, I don’t have a functional term/xterm-kitty.el right now. Maybe
one day, when/if I get fed up with X11 forwarding over a
less-than-lightspeed ssh connection.)



  reply	other threads:[~2021-12-06 18:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-03 11:34 . is undefined (when pressing C-.): is ssh behaving odd? Luca Ferrari
2021-12-03 14:33 ` Robert Pluim
2021-12-06 17:21   ` Luca Ferrari
2021-12-06 17:25     ` Robert Pluim
2021-12-06 18:02       ` Yuri Khan [this message]
2021-12-06 18:32         ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-06 18:43       ` Emanuel Berg via Users list for the GNU Emacs text editor

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=CAP_d_8VyHR0RJnm7-VEfvnXi1m1+_Vg4UierVC6_o37oe8a92g@mail.gmail.com \
    --to=yuri.v.khan@gmail.com \
    --cc=fluca1978@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=rpluim@gmail.com \
    /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. 
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).