Path: csiph.com!3.us.feeder.erje.net!feeder.erje.net!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail
From: Dennis Williamson <dennistwilliamson@gmail.com>
Newsgroups: gnu.bash.bug
Subject: Re: [readline] Multibyte invisible chars cause weird prompt length calculation issue
Date: Tue, 26 Nov 2019 10:23:28 -0600
Lines: 24
Approved: bug-bash@gnu.org
Message-ID: <mailman.2723.1574785424.13325.bug-bash@gnu.org>
References: <3dd641953467a3299265e479026fc40a7bb697d4.camel@mail.ru> <5DDC8DEC.7000602@tlinx.org> <7e3b83df07c20ccd75373f8804d2b0f2f930c773.camel@mail.ru> <CANaoh6JYE8PjT5xJQVCDOF8sCgkH5fQq=0XacM8h9PwNfJ-bwQ@mail.gmail.com> <0d24d2c3c8109cc3b801bddb5daa394725eb521f.camel@mail.ru> <CANaoh6+vuy=fL6_dvhnw=_+A7YrVHOrs_dLaSVQZ1uYoNeg76g@mail.gmail.com>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: bug-bash <bug-bash@gnu.org>
To: =?UTF-8?B?0JDQu9C10LrRgdC10Lkg0KjQuNC70LjQvQ==?= <rootlexx@mail.ru>
Envelope-to: bug-bash@gnu.org
In-Reply-To: <0d24d2c3c8109cc3b801bddb5daa394725eb521f.camel@mail.ru>
Precedence: list
Xref: csiph.com gnu.bash.bug:15657

On Tue, Nov 26, 2019, 9:50 AM =D0=90=D0=BB=D0=B5=D0=BA=D1=81=D0=B5=D0=B9 =
=D0=A8=D0=B8=D0=BB=D0=B8=D0=BD <rootlexx@mail.ru> wrote:

> =D0=92 =D0=92=D1=82, 26/11/2019 =D0=B2 07:35 -0600, Dennis Williamson =D0=
=BF=D0=B8=D1=88=D0=B5=D1=82:
> > 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.
>
> Ah, you meant that it should be:
>
> PS1=3D'\[\e]0;\]\u@\h:\w\[\a\]${debian_chroot:+($debian_chroot)}\[\033[01
> ;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
>
> Or the ']0;' part should be outside of '\[...\]', too?
>

No. As Greg pointed out, I missed the fact that the strings were part of
the escape sequence for the terminal title. Sorry for the confusion.

>