Re: suggestion: shell option for echo to not interpret any argument as an option

2023-07-28 Thread Chet Ramey
On 7/26/23 10:21 PM, Zachary Santer wrote: However, the man page for bash 5.2 only says the following about xpg_echo, in the section about shopt: "If set, the echo builtin expands backslash-escape sequences by default." It makes no mention of disabling option processing. Similarly, in the des

Re: comments inside command subst are handled inconsistently

2023-07-28 Thread Martin D Kealey
On Thu, 27 Jul 2023, 18:31 Denys Vlasenko, wrote: > Try these two commands: > > $ echo "Date: `date #comment`" > Date: Thu Jul 27 10:28:13 CEST 2023 > > $ echo "Date: $(date #comment)" > > )" > Date: Thu Jul 27 10:27:58 CEST 2023 > > > As you see, #comment is handled differently in `` and $(). >

[PATCH] use real compspec hash key for compopt output

2023-07-28 Thread Grisha Levit
The output of `compopt' in a running completion function is a command where the last word is usually the command for which the compspec was defined. However, if the current compspec was found by using the basename of the command word, or by invoking default completion, the output will use the type

Re: Tilde (~) in bash(1) is typeset incorrectly as Unicode character

2023-07-28 Thread Chet Ramey
ve. I'm attaching a straw man diff to the bash(1) page. If Chet likes it, I'm happy to prepare one against the bash devel branch. Applying the patch without any other changes to bash.1 results in $ groff -Tascii -P -c -I/usr/local/src/bash/bash-20230728/doc -man /usr/local/src/bash

Re: Tilde (~) in bash(1) is typeset incorrectly as Unicode character

2023-07-28 Thread G. Branden Robinson
Hi Chet, At 2023-07-28T15:15:48-0400, Chet Ramey wrote: > Applying the patch without any other changes to bash.1 results in > > $ groff -Tascii -P -c -I/usr/local/src/bash/bash-20230728/doc -man > /usr/local/src/bash/bash-20230728/doc/bash.1 > bash.0 > troff: /usr/local/src/