On 2/4/22 6:01 PM, Markus Schwarzenberg wrote:
I'd be happy with some command forcing redisplay, executed from
within the handler as a workaround.
On a new line? Duplicating what was there before the SIGALRM? I think
you'd be surprised at how many people would disagree with you.
Didn't mean
On Fri, 4 Feb 2022 17:37:06 -0500
Chet Ramey wrote:
> It depends on whether or not bracketed paste is active.
Must admit I wasn't aware of this. And will think about whether I need it.
> On 2/4/22 4:11 PM, Markus Schwarzenberg wrote:
> > On Fri, 4 Feb 2022 13:19:37 -0500
> > Chet Ramey wrote:
On 2/4/22 4:11 PM, Markus Schwarzenberg wrote:
On Fri, 4 Feb 2022 13:19:37 -0500
Chet Ramey wrote:
On 2/4/22 9:54 AM, Markus Schwarzenberg wrote:
Bash Version: 5.1
Patch Level: 8
Release Status: release
Description:
The position of the cursor changes to the first column when
bash,
On Fri, 4 Feb 2022 13:19:37 -0500
Chet Ramey wrote:
> On 2/4/22 9:54 AM, Markus Schwarzenberg wrote:
>
> > Bash Version: 5.1
> > Patch Level: 8
> > Release Status: release
> >
> > Description:
> > The position of the cursor changes to the first column when
> > bash, running inside xterm,
On 2/4/22 9:54 AM, Markus Schwarzenberg wrote:
Bash Version: 5.1
Patch Level: 8
Release Status: release
Description:
The position of the cursor changes to the first column when bash,
running inside xterm, receives the signal SIGALRM
Thanks for the report. It's readline and
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -O2 -flto=auto -ffat-lto-objects -fexceptions -g
-grecord-gcc-switches -pipe -Wall -Werror=format-security
-Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS
