[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Daemon/Client, Multiple Terminals, and `tty-erase-char'

From: Alexander Shukaev
Subject: Re: Daemon/Client, Multiple Terminals, and `tty-erase-char'
Date: Mon, 16 Dec 2019 15:51:10 +0000

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 <address@hidden> wrote:
>> Date: Mon, 16 Dec 2019 05:57:59 +0000
>> From: Alexander Shukaev <address@hidden>
>> 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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]