From: Ian Abbott <abbotti@mev.co.uk>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Backspace not working in terminal (using ssh)
Date: Thu, 21 Mar 2019 14:47:14 +0000 [thread overview]
Message-ID: <79d1dccf-9f46-2d44-b22e-b54e68983c6f@mev.co.uk> (raw)
In-Reply-To: <20190321133354.jtkxumdua3i43sf7@pengutronix.de>
On 21/03/2019 13:33, Michael Olbrich wrote:
> On Thu, Mar 21, 2019 at 12:46:40PM +0000, Ian Abbott wrote:
>> On 20/03/2019 15:41, Michael Olbrich wrote:
>>> On Wed, Mar 20, 2019 at 12:41:47PM +0000, Ian Abbott wrote:
>>>> On 20/03/2019 09:15, Dold, Wolfram wrote:
>>>>> On Tue, 2019-03-19 at 17:42 +0000, Ian Abbott wrote:
>>>>>> On 19/03/2019 12:33, Dold, Wolfram wrote:
>>>>>>> Hi Ian,
>>>>>>> On Tue, 2019-03-19 at 12:06 +0000, Ian Abbott wrote:
>>>>>>>> On 19/03/2019 09:17, Dold, Wolfram wrote:
>>>>>>>>> Hi there,
>>>>>>>>> when we connect via ssh to our embedded device, the backspace key does not work.
>>>>>>>>> During the analysis we found out that the passage
>>>>>>>>>
>>>>>>>>> # This fixes the backspace when telnetting in.
>>>>>>>>> if [ "$TERM" != "linux" ]; then
>>>>>>>>> stty erase ^H
>>>>>>>>> fi
>>>>>>>>>
>>>>>>>>> from the file '/etc/profile' contained in ptxdist.
>>>>>>>>>
>>>>>>>>> Now I want to ask, how best to fix this behavior?
>>>>>>>>> Can the passage simply be omitted? (At least the comment lets me assume that, because there 'telnet' is
>>>>>>>>> mentioned
>>>>>>>>> and
>>>>>>>>> that is no longer necessarily state of the art).
>>>>>>>>> Or does omitting it lead to other unwanted side effects?
>>>>>>>>>
>>>>>>>>> Any help would be appreciated.
>> [snip because it's getting a bit long]
>>
>>>> I've no idea why that bit of the /etc/profile file is there, but I guess it
>>>> must have suited one of the PTXdist developers at the time. A "git blame"
>>>> only revealed that the whole file was added in 2006, so I don't know how
>>>> relevant that part of it is today.
>>>
>>> This code was moved around some more. It was actually introduced in the
>>> initial import from CVS in 2003 :-). Telnet works just fine without this,
>>> so I guess this is no longer needed.
>>
>> Perhaps it was there for the Windows Telnet client which seems to send ASCII
>> BS when the "Backspace" key is pressed and ASCII DEL when the (less
>> conveniently placed) "Delete" key is pressed. This mimics the codes sent by
>> the VT-102 "Backspace" and "Delete" keys which were both conveniently
>> placed.
>>
>> The Windows telnet client has a -t option to set the terminal type to one of
>> "vt100", "vt52", "ansi", or "vtnt", but it doesn't pass the selected
>> terminal type to the server, and this doesn't seem to have any effect on the
>> codes sent by the "Backspace" and "Delete" keys. The TERM environment
>> variable ends up getting set to "vt102" by default on my PTXdist systems if
>> a terminal type hasn't been passed through by the Telnet client. I don't
>> know if that is configurable.
>>
>> The Windows Telnet client isn't installed by default, but can still be
>> installed as a "Windows Feature". I guess most people who used it would
>> have switched to something like PuTTY by now.
>
> I'm pretty sure it was a Linux issue. I remember having problems like this
> a long time ago.
I guess it used to do `stty erase ^H` always and an exception was added
later for terminal type "linux". The Linux vt console sends ASCII DEL
for the Backspace key, and ASCII ESC [ 3 ~ for the Delete key, so that
seems like it was a reasonably cautious change at the time.
>>> I'll be happy to apply a patch that removes this.
>>
>> I'm worried that doing so might annoy some people who expect the existing
>> behavior.
>
> I'd rather fix a real problem. If it causes issues, then we'll try to find
> a solution.
I suppose using the GNU coreutils default value for the stty erase
character ( ^? (ASCII DEL) by default) is likely to cause the least
problems overall. This also seems to be the default for FreeBSD
(although FreeBSD stty also has an "erase2" option set to ^H (ASCII BS)
by default).
--
-=( Ian Abbott <abbotti@mev.co.uk> || Web: www.mev.co.uk )=-
-=( MEV Ltd. is a company registered in England & Wales. )=-
-=( Registered number: 02862268. Registered address: )=-
-=( 15 West Park Road, Bramhall, STOCKPORT, SK7 3JZ, UK. )=-
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2019-03-21 14:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 9:17 Dold, Wolfram
2019-03-19 10:31 ` Roland Hieber
2019-03-19 10:57 ` Dold, Wolfram
2019-03-19 12:06 ` Ian Abbott
2019-03-19 12:33 ` Dold, Wolfram
2019-03-19 17:42 ` Ian Abbott
2019-03-20 9:15 ` Dold, Wolfram
2019-03-20 12:41 ` Ian Abbott
2019-03-20 15:41 ` Michael Olbrich
2019-03-21 12:46 ` Ian Abbott
2019-03-21 13:33 ` Michael Olbrich
2019-03-21 14:47 ` Ian Abbott [this message]
2019-03-21 15:24 ` Ian Abbott
2019-03-22 7:55 ` Michael Olbrich
2019-03-22 10:16 ` Ian Abbott
2019-03-22 12:30 ` [ptxdist] [PATCH] projectroot: remove setting stty erase character to "^H" Dold, Wolfram
2019-03-21 10:45 ` [ptxdist] Backspace not working in terminal (using ssh) Dold, Wolfram
2019-03-21 11:26 ` Michael Olbrich
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=79d1dccf-9f46-2d44-b22e-b54e68983c6f@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=ptxdist@pengutronix.de \
/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