On 12/20/24 7:30 PM, Lawrence Velázquez wrote:
On Fri, Dec 20, 2024, at 8:09 AM, Greg Wooledge wrote:
help -d cdoes not exactly match anything, so it's treated like c\*
Is this documented somewhere? I'm not seeing anything about it in
the man page or texinfo manual.
If the argument cont
On Fri, Dec 20, 2024 at 19:30:49 -0500, Lawrence Velázquez wrote:
> On Fri, Dec 20, 2024, at 8:09 AM, Greg Wooledge wrote:
> > help -d cdoes not exactly match anything, so it's treated like c\*
>
> Is this documented somewhere? I'm not seeing anything about it in
> the man page or texinfo man
On Fri, Dec 20, 2024, at 8:09 AM, Greg Wooledge wrote:
> help -d cdoes not exactly match anything, so it's treated like c\*
Is this documented somewhere? I'm not seeing anything about it in
the man page or texinfo manual.
--
vq
On Fri, Dec 20, 2024 at 04:50:17 -0800, Wiley Young wrote:
> For some reason, while `help -d 'c'` prints the same thing as `help -c
> 'c*'` (note the asterisk), the same is not true when the character is
> left-bracket: `help -c '[*'.
Why did you expect them to be the same? Assuming you meant -d
Testing how bash's help builtin responds to each character.
For some reason, while `help -d 'c'` prints the same thing as `help -c
'c*'` (note the asterisk), the same is not true when the character is
left-bracket: `help -c '[*'. This issue persists on bash 5.3 beta.
# Input:
[liveuser@fedora ~]
