mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Dold, Wolfram" <Wolfram.Dold@allegion.com>
To: "Dold, Wolfram" <Wolfram.Dold@allegion.com>,
	"rhi@pengutronix.de" <rhi@pengutronix.de>
Cc: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] Backspace not working in terminal (using ssh)
Date: Tue, 19 Mar 2019 10:57:51 +0000	[thread overview]
Message-ID: <64aa123c39516e0fff3e0a0da6cbd077485d8462.camel@allegion.com> (raw)
In-Reply-To: <20190319103143.futvjcehpivgxmch@pengutronix.de>

Hi Roland,
thank's for the quick reply.
On Tue, 2019-03-19 at 11:31 +0100, Roland Hieber wrote:
> Hi Wolfram,
> 
> there are historically different handlings of backspace, one is
> Ctrl-H, as mentioned by you below. The exact setting depends on the
> terminal emulator (some terminal emulators can also switch the
> behaviour, e.g. in putty, look under Terminal -> Keyboard). 
I saw that already. Our service technicians use putty under Windows.
The default setting on backspace for ssh connections in putty is '^?'.
Sure, we could tell them, change that setting, but from experience
some would overlook it or forget it or whatever.

The default setting for gnome-terminal is also '^?'.

So a working solution would be to delete the passage from the /etc/profile file.
What I don't like is that we then have a solution that differs from the ptxdist standard.
So the question is, is it imaginable that one of the next versions of ptxdist will 
no longer contain this passage?

Regards, Wolfram


> If backspace
> works for you without the stty line, then there is no harm in leaving it
> out, but the backspace behaviour could be different when connecting to
> the board with a different terminal emulator.
> 
> For reference, when I type `stty -a` on my xterm, it says :
> 
>     erase = ^?;
> 
>  - Roland
> 
> On Tue, Mar 19, 2019 at 09:17:13AM +0000, 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.
> > -- 
> > Regards,
> > Wolfram Dold
> > 
> > _______________________________________________
> > ptxdist mailing list
> > ptxdist@pengutronix.de
> 
> 
-- 
Regards / Mit den besten Grüßen,
Wolfram Dold
 
Firmware Developer
Phone:  +49 (0)7464/382-340

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2019-03-19 10:57 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 [this message]
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
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=64aa123c39516e0fff3e0a0da6cbd077485d8462.camel@allegion.com \
    --to=wolfram.dold@allegion.com \
    --cc=ptxdist@pengutronix.de \
    --cc=rhi@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