From: Andreas Schwab <schwab@suse.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs@Alexander.Shukaev.name, emacs-devel@gnu.org
Subject: Re: Daemon/Client, Multiple Terminals, and `tty-erase-char'
Date: Mon, 16 Dec 2019 20:19:29 +0100 [thread overview]
Message-ID: <87o8w8xem6.fsf@igel.home> (raw)
In-Reply-To: <83pngo3yzi.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 16 Dec 2019 20:29:53 +0200")
On Dez 16 2019, Eli Zaretskii wrote:
>> From: Andreas Schwab <schwab@suse.de>
>> Cc: emacs@Alexander.Shukaev.name, emacs-devel@gnu.org
>> Date: Mon, 16 Dec 2019 19:17:23 +0100
>>
>> On Dez 16 2019, Eli Zaretskii wrote:
>>
>> > OK, but still, if one calls, say, set-input-meta-mode, tty-erase-char
>> > will be reset as appropriate for the TERMINAL argument, and that is
>> > not necessarily the last-frame value.
>>
>> It is the last-frame value when a frame was just created on a new
>> terminal, which is why normal-erase-is-backspace-setup-frame works by
>> chance.
>
> I agree, but the "by chance" part worries me. This whole business
> looks quite fragile.
tty-erase-char should really be a function with a terminal parameter.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
prev parent reply other threads:[~2019-12-16 19:19 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
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 [this message]
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=87o8w8xem6.fsf@igel.home \
--to=schwab@suse.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=emacs@Alexander.Shukaev.name \
/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.