Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #16406 > unrolled thread

Re: Backspace echoed incorrectly with TERM=garbage

Started byBryan Henderson <bryanh@giraffe-data.com>
First post2020-06-18 20:53 +0000
Last post2020-06-18 20:53 +0000
Articles 1 — 1 participant

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Backspace echoed incorrectly with TERM=garbage Bryan Henderson <bryanh@giraffe-data.com> - 2020-06-18 20:53 +0000

#16406 — Re: Backspace echoed incorrectly with TERM=garbage

FromBryan Henderson <bryanh@giraffe-data.com>
Date2020-06-18 20:53 +0000
SubjectRe: Backspace echoed incorrectly with TERM=garbage
Message-ID<mailman.81.1592515819.2574.bug-bash@gnu.org>
> I imagine that depends on your terminal and your stty settings. On MacOS with
> Bash 5 in Terminal.app what you describe doesn't happen for me. What terminal
> are you using? What is the output of stty -a with respect to erase? What do
> you get in that setup when you press Ctrl-V then Backspace?

Thanks for trying to reproduce it.

I see this with an X.org xterm under Linux and a Linux virtual console, both
through SSH (Openssh), and Putty in Windows, via Putty's SSH.

To simplify things, I set my erase key to "q" (stty erase q).  ctl-V q
confirms terminal sends q when I type it.  Behavior is the same - q functions
as backspace, gets echoed as space.  In Bash 4, it gets echoed as backspace.

I used 'script' to verify that the terminal is receiving an ASCII space
(0x20) character.

-- 
Bryan Henderson                                   San Jose, California

[toc] | [standalone]


Back to top | Article view | gnu.bash.bug


csiph-web