Re: [gnu.org #1838744] Bash Manual, 3.6.2 Redirecting Inputs, SUGGESTION

2022-05-20 Thread Lawrence Velázquez
On Fri, May 20, 2022, at 7:01 PM, Lawrence Velázquez wrote: > On Fri, May 20, 2022, at 2:06 PM, Therese Godefroy via RT wrote: >> I'm going to tell him there is no guarantee that this can be changed. >> For one thing, it would be difficult to find a letter that doesn't >> take an unwanted meaning w

Re: [gnu.org #1838744] Bash Manual, 3.6.2 Redirecting Inputs, SUGGESTION

2022-05-20 Thread Lawrence Velázquez
On Fri, May 20, 2022, at 2:06 PM, Therese Godefroy via RT wrote: > I'm going to tell him there is no guarantee that this can be changed. > For one thing, it would be difficult to find a letter that doesn't > take an unwanted meaning when associated with "word". Perhaps something like "num" or "fd"

[gnu.org #1838744] Bash Manual, 3.6.2 Redirecting Inputs, SUGGESTION

2022-05-20 Thread Therese Godefroy via RT
Hello Bash maintainers, Here is a challenging ticket. The requester complains about the association of "n" and "word" in "Redirecting Input" (image.png is a screenshot of this chapter with the examples emphasized): https://www.gnu.org/software/bash/manual/bash.html#Redirecting-Input I'm going to

Re: UP does not invoke line history immediately

2022-05-20 Thread Martin D Kealey
Hi Andrea This would appear to be an issue with the readline library, rather than Bash itself. As you've noted that it's timing-sensitive, I'm wondering if it's related to bytes received immediately prior, so to investigate this would it be possible to run Bash inside a "script" session, until y

UP does not invoke line history immediately

2022-05-20 Thread Andrea Monaco
In rare cases, the following happens to me: when I press UP and then RET to execute the last command line, and the two presses are close enough in time, bash takes the UP key as input without invoking history, so it tries to execute something like '^[[A'. This is minor, but it seems a bug to me.

Re: complete -p does not quote function names correctly.

2022-05-20 Thread Koichi Murase
> Description: > bash allows declaring functions with a name that contains `*'. > In the output of `complete -p', those function names will not be > quoted which makes the output of `complete -p' output not safe > to pass to `eval' or output to a file that will be re

complete -p does not quote function names correctly.

2022-05-20 Thread Emanuele Torre
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -DDEFAULT_PATH_VALUE='/usr/local/sbin:/usr/local/bin:/usr/bin' -DSTANDARD_UTILS_PATH='/usr/bin' -DSYS_BASHRC='/etc/bash