please .. how what .. ?
On Thu, Jan 9, 2025, 11:15 PM Wiley Young wrote:
> On Wed, 8 Jan 2025 08:44:06 +1000,
> Martin D Kealey wrote:
>
> > I invite anyone to provide an example of how
>
> If the documentation changes at all, I think just a "See also..." might be
> enough.
>
> Wuley
>
On 1/9/25 3:41 PM, Jeff Ketchum wrote:
Excellent! I can stop trying to dig in to the code and understand where all
the word expansions happen.
So strange to find those one off bugs, and great that it was only one.
Do you have, or working on a patch that can be applied to a build?
It will be
On Wed, 8 Jan 2025 08:44:06 +1000,
Martin D Kealey wrote:
> I invite anyone to provide an example of how
If the documentation changes at all, I think just a "See also..." might be
enough.
Wuley
Andreas Schwab writes:
>> It does seem like "bind" could be improved by providing an option that
>> shows all of the keysequences and what they are bound to.
>
> bind -p | sort
There's "bind -P", which lists "function names" and bindings, and then
there's "bind -S", which lists "key sequences bou
On 1/8/25 1:25 PM, Jeff Ketchum wrote:
I ran into a strange bug using newer versions of bash, I haven't isolated
it to a specific release.
OS1: Oracle Enterprise linux 9,4 bash 5.1.8(1)
OS2: Gentoo linux bash version 5.2.37
older bash:
OS3: centos linux 7.9 bash 4.2.46(2)
In using unicode group
Excellent! I can stop trying to dig in to the code and understand where all
the word expansions happen.
So strange to find those one off bugs, and great that it was only one.
Do you have, or working on a patch that can be applied to a build?
Thanks
Jeff
On Thu, Jan 9, 2025 at 1:20 PM Chet Ramey
