@Andreas
Have it solved by following that manual page and using "\[ ... \]"
combination. Thanks for the hint!
By the way, apparently the content about "non-printing characters" in that
man page has not been modified across the several versions of Bash, for
example in my machine, "3.2.57(1)-releas
i solve this by shopt -s nullglob
On Sun, Mar 20, 2022, 22:07 Alexey via Bug reports for the GNU Bourne Again
SHell wrote:
> Hello.
>
> Machine: x86_64
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -g -O2 -fstack-protector-strong -Wformat
> -Werror=format-security -Wall
> uname output: L
nullglob is not applicable in this situation, because no 'Pathname
Expansion' is occur.
On 2022-03-21 14:40, Alex fxmbsw7 Ratchev wrote:
i solve this by shopt -s nullglob
On Sun, Mar 20, 2022, 22:07 Alexey via Bug reports for the GNU Bourne
Again SHell wrote:
Hello.
Machine: x86_64
On Mon, Mar 21, 2022 at 05:00:29PM +0800, Michaelll Lee wrote:
> By the way, apparently the content about "non-printing characters" in that
> man page has not been modified across the several versions of Bash, for
> example in my machine, "3.2.57(1)-release" and "5.1.0(1)-release" share
> nearly t
Stop. Posting. Upside-down.
> > On Sun, Mar 20, 2022, 22:07 Alexey via Bug reports for the GNU Bourne
> > > Repeat-By:
> > > Code: x=("/"); for i in "${x[@]%/}"; do echo "i is '$i'"; done
> > > Result: none
> > > Expected result: i is ''
> On 2022-03-21 14:40, Alex fxmbsw7 Ratchev wrote:
> > i
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-redhat-linux-gnu'
-DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/locale'
I can add one more example, which change array size while it's not
expected behavior:
x=("/"); y=("${x[@]%/}"); echo "x size: ${#x[@]}, y size: ${#y[@]}"
Goal of this example show that it is not only for loop issue.
On 3/19/22 1:07 PM, Taqras via Bug reports for the GNU Bourne Again SHell
wrote:
Bash Version: 5.1
Patch Level: 16
Release Status: release
Description:
PS0:
The value of this parameter is expanded like PS1 and displayed by
interactive shells after reading a command and befor
On Mon, Mar 21, 2022 at 4:01 AM Michaelll Lee wrote:
> . . .
> While using non-printing characters without "\[...\]" proves to be fine in
> versions prior to 5.x.x (e.g., many suggestions from some online forums
> have suggested "PS1=\e[0m" for using ANSI escape code in the prompt), the
> same co
On 3/21/22 5:00 AM, Michaelll Lee wrote:
While using non-printing characters without "\[...\]" proves to be fine in
versions prior to 5.x.x (e.g., many suggestions from some online forums
have suggested "PS1=\e[0m" for using ANSI escape code in the prompt), the
same configuration in 5.x.x is not
On Mon, Mar 21, 2022, at 8:50 AM, Alexey via Bug reports for the GNU Bourne
Again SHell wrote:
> I can add one more example, which change array size while it's not
> expected behavior:
> x=("/"); y=("${x[@]%/}"); echo "x size: ${#x[@]}, y size: ${#y[@]}"
This discrepancy seems to have been intro
After setting PS1 to the following value and resizing window to 90 or
89 columns, display of then typed characters becomes broken.
PS1=$'f
\\[\E[0;1;37m\\]\\$\\[\E[0m\\] '
It may or may not need backspace to b
On Mon, Mar 21, 2022 at 02:47:12PM -0400, Lawrence Velázquez wrote:
> On Mon, Mar 21, 2022, at 8:50 AM, Alexey via Bug reports for the GNU Bourne
> Again SHell wrote:
> > I can add one more example, which change array size while it's not
> > expected behavior:
> > x=("/"); y=("${x[@]%/}"); echo "
On 3/21/22 2:49 PM, konsolebox wrote:
After setting PS1 to the following value and resizing window to 90 or
89 columns, display of then typed characters becomes broken.
PS1=$'f
\\[\E[0;1;37m\\]\\$\\[\E[0m\\]
Hi,
Is there a plan for a 2nd 5.2 alpha? A number of reported bugs have been
addressed since and it may help resolve duplicates.
Best,
sam
signature.asc
Description: Message signed with OpenPGP
On 3/21/22 3:14 PM, Sam James wrote:
Hi,
Is there a plan for a 2nd 5.2 alpha? A number of reported bugs have been
addressed since and it may help resolve duplicates.
The next release will be 5.2-beta. You can always use the devel branch for
the latest code.
--
``The lyf so short, the craft so
On Mon, Mar 21, 2022 at 7:11 PM Chet Ramey wrote:
> Isn't this the same as
>
> https://lists.gnu.org/archive/html/bug-readline/2022-02/msg00038.html ?
>
> That's already fixed.
I'm sorry I didn't check. Yes it's already fixed.
--
konsolebox
On Sat, Feb 19, 2022 at 9:34 PM Chet Ramey wrote:
> Thanks for the report. This is the result of needing to clean up parser
> state before recursively calling it to parse the command substitution.
Just tested devel. This one's fixed as well.
--
konsolebox
On Mar 21, 2022, 9:47 PM Chet Ramey wrote:
> Unless told otherwise, it assumes that every character it outputs contributes
> to that physical cursor position.
Thank you Sir, for pointing out this clearly, and now I think my
previous thoughts would be my misunderstanding.
On Mon, Mar 21, 2022 at
On Mar 21, 2022, 9:39 PM Dennis Williamson
wrote:
>
> Note that the difference you see in Bash 5 is due to new paste behavior.
>From the perspective from users, would be more appropriate to see a hint
for this new kind of behavior in man page/manual. Anyway, thanks for the
clarification.
On Mo
20 matches
Mail list logo
