Re: Weird command line editing issues with Bash

[Steve Wechsler]

\033]0;${STY##*.}\007\[\e[00;32m\][${STY##*.}|\u@<hostname> \W]\[\e[00m\]$

On Thu, Nov 9, 2023 at 4:13 PM Marcin Cieslak <saper@saper.info> wrote:

On Thu, 9 Nov 2023, Steve Wechsler wrote:

> Frequently I get odd results when using Emacs mode command line editing
> in Bash.
>
> 1) Sometimes after scrolling back in my history, the first 9 characters of
> the line will remain in place, and the beginning-of-line position moves 9
> characters to the right. So, for example, if I scrolled past an entry that
> started with "awk '{if ($1 > 100 ) {print $2}', when pressing Ctrl-U, the
> cursor will be positioned after 'awk '{if '. It only seems to be affected
> by certain longer entries in the history.
> 2) When typing a line that's longer than my terminal is wide (including the
> command prompt), the cursor will return to the beginning of the line, but
> it will not line feed, so it starts overwriting the text that is already
> there. If I make my terminal wider and press Ctrl-L, the line can be edited
> normally, until it needs to wrap again, then the problem repeats.
>
> Once I exit screen, command line editing in Bash works properly. The Emacs
> editor itself seems to have no issues, nor does vim.
>
> I'm using PuTTy on Windows. $TERM is 'xterm'. I've tried substituting
> 'vt100' but it didn't fix the problem. Screen  v4.09.00 on Centos7, Bash
> version is 4.2.46(2).

What is your $PS1 ?