From: Ian Abbott <abbotti@mev.co.uk>
To: ptxdist@pengutronix.de, "Dold, Wolfram" <Wolfram.Dold@allegion.com>
Subject: Re: [ptxdist] Backspace not working in terminal (using ssh)
Date: Tue, 19 Mar 2019 12:06:19 +0000 [thread overview]
Message-ID: <b31f5ba5-1010-aa89-9d27-3ae45e3d0614@mev.co.uk> (raw)
In-Reply-To: <0d26df920a3db4f805d5563f4aabb2bf1678056c.camel@allegion.com>
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.
>
Code can interpret input characters in various ways independently of the
stty settings. For example, if the "Command Line Editing" feature is
enabled in the Busybox configuration, the Busybox "ash" and "hush"
shells' interactive line editing will handle both ASCII DEL and ASCII BS
as a "backspace" operation. This can be enabled in the PTXdist
menuconfig via:
Shell & Console Tools --->
-*- busybox --->
Settings --->
[*] Command Line Editing
This sets "PTXCONF_BUSYBOX_FEATURE_EDITING=y" in the ptxconfig file.
If you are using Bash or some other other program with READLINE support,
I think it handles ASCII BS and ASCII DEL similarly to Busybox's command
line editing feature.
--
-=( 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-19 12:06 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 [this message]
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
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=b31f5ba5-1010-aa89-9d27-3ae45e3d0614@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=Wolfram.Dold@allegion.com \
--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