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


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

Re: [readline] Multibyte invisible chars cause weird prompt length calculation issue

Started byDennis Williamson <dennistwilliamson@gmail.com>
First post2019-11-26 07:35 -0600
Last post2019-11-26 07:35 -0600
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: [readline] Multibyte invisible chars cause weird prompt length calculation issue Dennis Williamson <dennistwilliamson@gmail.com> - 2019-11-26 07:35 -0600

#15653 — Re: [readline] Multibyte invisible chars cause weird prompt length calculation issue

FromDennis Williamson <dennistwilliamson@gmail.com>
Date2019-11-26 07:35 -0600
SubjectRe: [readline] Multibyte invisible chars cause weird prompt length calculation issue
Message-ID<mailman.2694.1574775333.13325.bug-bash@gnu.org>
On Tue, Nov 26, 2019, 5:46 AM Алексей Шилин <rootlexx@mail.ru> wrote:

> В Пн, 25/11/2019 в 18:29 -0800, L A Walsh пишет:
> >     Multi-byte or not, invisible characters need to be enclosed
> > as documented under 'PROMPTING':
> >
> >      \[     begin a sequence of non-printing characters, which  could
> >             be  used  to  embed  a terminal control sequence into the
> >             prompt
> >      \]     end a sequence of non-printing characters
> >
>
> I know that.
>
> And they *are* enclosed: PS1='\[\e]0;\u@\h: \w\a\]${debian_chroot...
>                               ^~                ^~
>
> As expected, they are not being printed -- but for some reason lead to
> the described issue.
>
>

You have printable characters enclosed. For example, \u. _Each_ sequence of
unprintable characters needs to be separately enclosed _without_ enclosing
the printable ones.

The first part of your prompt is what needs to be corrected. The latter
part after "debian_chroot" is correct.

>

[toc] | [standalone]


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


csiph-web