unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alexander Shukaev <emacs@Alexander.Shukaev.name>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Daemon/Client, Multiple Terminals, and `tty-erase-char'
Date: Mon, 16 Dec 2019 15:51:10 +0000	[thread overview]
Message-ID: <8D9B8C19-3DF8-4D21-9778-B1E50AFED0F4@Alexander.Shukaev.name> (raw)
In-Reply-To: <83eex45lvh.fsf@gnu.org>

[-- Attachment #1: Type: text/html, Size: 2179 bytes --]

[-- Attachment #2: Type: text/plain, Size: 1675 bytes --]

I don't think this can be deprecated.  That logic to determine the behavior of backspace and delete keys is important.  I saw 'terminal-parameter' being used there, plus there are variables like 'local-function-key-map', which is supposed to be per-frame as that is it's purpose in the first place, and it even seems to have been introduced exactly for this 'normal-erase-is-backspace' use case because it's only directly mapped in that function.  So I expected 'tty-erase-char' to also be frame-specific, otherwise, this is indeed unfinished and won't work even in the simple case of having both one GUI and one terminal clients at the same time.

On December 16, 2019 4:30:10 PM GMT+01:00, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Mon, 16 Dec 2019 05:57:59 +0000
>> From: Alexander Shukaev <emacs@Alexander.Shukaev.name>
>> 
>> The expectation is that 'normal-erase-is-backspace' does the right
>thing in different terminal of course. But
>> that's just an example, and aside from it, this variable seems to be
>terminal-specific due to its nature.
>
>Do you have a real-life situation where it is important to have
>'normal-erase-is-backspace' to be different on different terminals?
>
>We have some infrastructure to record the value in a terminal
>parameter, but I don't see the mode function called when we switch
>frames.  And a mode cannot be terminal- or frame-specific.
>
>So it looks like if someone intended to make this work differently on
>different terminals, they didn't finish the job.  Or maybe I missing
>something; but if not, the question is whether we really need this
>stuff nowadays, or is it obsolete and should be removed at some future
>point.

  reply	other threads:[~2019-12-16 15:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-16  4:00 Daemon/Client, Multiple Terminals, and `tty-erase-char' Alexander Shukaev
2019-12-16  5:19 ` Eli Zaretskii
2019-12-16  5:57   ` Alexander Shukaev
2019-12-16 15:30     ` Eli Zaretskii
2019-12-16 15:51       ` Alexander Shukaev [this message]
2019-12-16 16:02   ` Andreas Schwab
2019-12-16 16:36     ` Alexander Shukaev
2019-12-16 17:01     ` Eli Zaretskii
2019-12-16 17:15       ` Andreas Schwab
2019-12-16 17:44         ` Eli Zaretskii
2019-12-16 18:17           ` Andreas Schwab
2019-12-16 18:29             ` Eli Zaretskii
2019-12-16 19:19               ` Andreas Schwab

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=8D9B8C19-3DF8-4D21-9778-B1E50AFED0F4@Alexander.Shukaev.name \
    --to=emacs@alexander.shukaev.name \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.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 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).