On 12/3/19 1:43 PM, Алексей Шилин wrote:
> PS1='\[\e]0;тестоваястрока\a\]test prompt\$ '
This is really the problem: the invisible multibyte characters in the
prompt are not correctly counted in all cases and throw off the cursor
positioning calculations. That problem is worse when the prompt
comp
В Ср, 27/11/2019 в 20:29 -0500, Chet Ramey пишет:
> I poked around enough and found the cause. There will be a
> fix in the next devel branch push.
The first issue with the line not being cleared is indeed fixed.
Thanks!
The second one with incorrect history entry output position after e.g.
End i
On 11/27/19 3:19 PM, Алексей Шилин wrote:
> В Ср, 27/11/2019 в 11:48 -0500, Chet Ramey пишет:
>> The reason I ask is that I can (unsurprisingly) reproduce multiple
>> redisplay issues if the newline after the `\h:' is present, but none
>> when $PS1 doesn't contain any newlines.
>
> You mean you ca
В Ср, 27/11/2019 в 20:29 -0500, Chet Ramey пишет:
> I poked around enough and found the cause. There will be a
> fix in the next devel branch push.
That's awesome! Thank you *very* much!
В Ср, 27/11/2019 в 11:48 -0500, Chet Ramey пишет:
> The reason I ask is that I can (unsurprisingly) reproduce multiple
> redisplay issues if the newline after the `\h:' is present, but none
> when $PS1 doesn't contain any newlines.
You mean you can't reproduce the issue? That's weird, since I can
> Debian's /etc/skel/.bashrc contains these lines:
>
> if [ "$color_prompt" = yes ]; then
>
> PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m
> \]:\[\033[01;34m\]\w\[\033[00m\]\$
> '
> else
> PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
> fi
>
> The leading
On 11/27/19 11:24 AM, Алексей Шилин wrote:
В Ср, 27/11/2019 в 11:02 -0500, Chet Ramey пишет:
On 11/25/19 10:05 AM, Алексей Шилин wrote:
Bash Version: 5.0
Patch Level: 11
Release Status: release
Description:
I'm using the following PS1 prompt (Debian's default for normal
users):
\[\e]0;\u@\h
В Ср, 27/11/2019 в 11:02 -0500, Chet Ramey пишет:
> On 11/25/19 10:05 AM, Алексей Шилин wrote:
>
> > Bash Version: 5.0
> > Patch Level: 11
> > Release Status: release
> >
> > Description:
> >
> > I'm using the following PS1 prompt (Debian's default for normal
> > users):
> >
> > \[\e]0;\u@\h:
>
On Wed, Nov 27, 2019 at 11:02:49AM -0500, Chet Ramey wrote:
> On 11/25/19 10:05 AM, Алексей Шилин wrote:
> > I'm using the following PS1 prompt (Debian's default for normal users):
> >
> > \[\e]0;\u@\h:
> > \w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\
> > ]:\[\033[01;34m
On 11/25/19 10:05 AM, Алексей Шилин wrote:
Bash Version: 5.0
Patch Level: 11
Release Status: release
Description:
I'm using the following PS1 prompt (Debian's default for normal users):
\[\e]0;\u@\h:
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\
]:\[\033[01;34m\]\w\[
On Tue, Nov 26, 2019, 9:50 AM Алексей Шилин wrote:
> В Вт, 26/11/2019 в 07:35 -0600, Dennis Williamson пишет:
> > You have printable characters enclosed. For example, \u. _Each_
> > sequence of unprintable characters needs to be separately enclosed
> > _without_ enclosing the printable ones.
> >
В Вт, 26/11/2019 в 07:35 -0600, Dennis Williamson пишет:
> 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.
В Вт, 26/11/2019 в 07:35 -0600, Dennis Williamson пишет:
> You have printable characters enclosed. For example, \u. _Each_
> sequence of unprintable characters needs to be separately enclosed
> _without_ enclosing the printable ones.
They're all part of the escape sequence. Try:
printf '\e]0;hell
On Tue, Nov 26, 2019 at 07:35:09AM -0600, Dennis Williamson wrote:
> On Tue, Nov 26, 2019, 5:46 AM Алексей Шилин wrote:
> > And they *are* enclosed: PS1='\[\e]0;\u@\h: \w\a\]${debian_chroot...
>
> You have printable characters enclosed. For example, \u. _Each_ sequence of
> unprintable characters
On Tue, Nov 26, 2019, 5:46 AM Алексей Шилин 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
> >
В Пн, 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
>
On 2019/11/25 07:05, wrote:
> # As you see, now everything works as expected i.e. the issue seems
> # to be in the way readline is handling multibyte invisible characters
> # in a prompt, *probably* in the rl_redisplay() function.
>
Multi-byte or not, invisible characters need to
Configuration Information:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2 -fdebug-prefix-map=/build/bash-REtn6r/bash-
5.0=. -fstack-protector-strong -Wformat -Werror=format-security -Wall
-Wno-parentheses -Wno-format-security
uname output: Linux sid-readline 4.19.0-6-amd64 #
18 matches
Mail list logo
