Re: Weird command line editing issues with Bash

2023-11-09 Thread Michael Grant
Note: Wrapping the tput output in \[ \] is recommended by the Bash man page. This helps Bash ignore non-printable characters so that it correctly calculates the size of the prompt. https://wiki.archlinux.org/title/Bash/Prompt_customization

Re: Weird command line editing issues with Bash

2023-11-09 Thread Steve Wechsler
\033]0;${STY##*.}\007\[\e[00;32m\][${STY##*.}|\u@ \W]\[\e[00m\]$ On Thu, Nov 9, 2023 at 4:13 PM Marcin Cieslak 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 i

Re: Weird command line editing issues with Bash

2023-11-09 Thread Marcin Cieslak
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

Weird command line editing issues with Bash

2023-11-09 Thread Steve Wechsler
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 entr