On 11/22/10 5:24 PM, Dennis Williamson wrote:
> In Bash 4.1 downloaded and patched from the case.edu Bash site, when I
> do bind -v I see "set blink-matching-paren on" (and have non-working
> paren matching) without having changed any compile-time settings and
> with no corresponding command in any
In Bash 4.1 downloaded and patched from the case.edu Bash site, when I
do bind -v I see "set blink-matching-paren on" (and have non-working
paren matching) without having changed any compile-time settings and
with no corresponding command in any startup files.
So I don't know how it got (half) ena
On 11/22/10 3:36 PM, Dennis Williamson wrote:
> When I do
>
> bind -v
>
> one of the settings I see is
>
> set blink-matching-paren on
It's not supposed to be enabled by default. (It's also not documented.)
Since a function has to run to do the appropriate things when it's enabled,
and isn't r
When I do
bind -v
one of the settings I see is
set blink-matching-paren on
but I don't get any blinking when I type closing parentheses at the
command line.
If I do
bind 'set blink-matching-paren on'
or have
set blink-matching-paren on
in my ~/.inputrc
explicitly, then it works.
Why does
