On Fri, Sep 13, 2024 at 3:24 PM Chet Ramey wrote:
>
> > I considered that maybe it
> > would only do this in response to being set directly, but neither
> > ~/.bashrc nor /etc/bash.bashrc on my system include it, nor any other
> > file I can find. Unless this has been changed between that version
On 9/14/24 2:45 PM, G. Branden Robinson wrote:
At 2024-09-13T15:24:15-0400, Chet Ramey wrote:
It has no effects in its default state. If you don't change it, nothing
happens. If you change it, you change `bell-style' instead.
The fact that its usage continues suggests documenting it as
depreca
At 2024-09-13T15:24:15-0400, Chet Ramey wrote:
> It has no effects in its default state. If you don't change it, nothing
> happens. If you change it, you change `bell-style' instead.
>
> > The fact that its usage continues suggests documenting it as
> > deprecated would be beneficial.
>
> Maybe.
On 9/13/24 11:00 AM, John Devin wrote:
As you said, it's been deprecated -- and undocumented -- for over 30 years
(and remains only for backwards compatibility). There's no reason to
document it.
I understand it's been superseded, but I do want to point this out:
running `bind -v` in bash 5.2
Hey Chet,
Thanks for getting back so fast. Just a couple points to make.
On Thu, Sep 12, 2024 at 4:38 PM Chet Ramey wrote:
>
> On 9/11/24 3:19 PM, John Devin wrote:
> > While hunting down some problems on a terminal, I ran across the
> > option 'prefer-visible-bell'. It took me some time looking
On 9/11/24 3:19 PM, John Devin wrote:
Hello all,
Sorry in advance if this is poorly formatted; I used plain-text mode
in gmail but who knows if that works properly.
It looks just fine.
While hunting down some problems on a terminal, I ran across the
option 'prefer-visible-bell'. It took me
Hello all,
Sorry in advance if this is poorly formatted; I used plain-text mode
in gmail but who knows if that works properly.
While hunting down some problems on a terminal, I ran across the
option 'prefer-visible-bell'. It took me some time looking into this
before finding out it was deprecated
On 7/28/20 4:21 AM, Daniel Molina wrote:
> On 27/7/20 22:09, Chet Ramey wrote:
>> On 7/25/20 12:21 PM, Daniel Molina wrote:
>>> Hi,
>>>
>>> I found some aspects of readline documentation that seem inconsistent to
>>> me and I wanted to share them.
&g
On 27/7/20 22:09, Chet Ramey wrote:
> On 7/25/20 12:21 PM, Daniel Molina wrote:
>> Hi,
>>
>> I found some aspects of readline documentation that seem inconsistent to
>> me and I wanted to share them.
>>
>> 1. The difference between backward-kill-line and
On 7/25/20 12:21 PM, Daniel Molina wrote:
> Hi,
>
> I found some aspects of readline documentation that seem inconsistent to
> me and I wanted to share them.
>
> 1. The difference between backward-kill-line and unix-line-discard
> readline commands.
>
Hi,
I found some aspects of readline documentation that seem inconsistent to
me and I wanted to share them.
1. The difference between backward-kill-line and unix-line-discard
readline commands.
Documentation states:
backward-kill-line (C-x Rubout)
Kill backward to the
On 5/25/18 9:50 PM, Jorge Maldonado Ventura wrote:
> There is an unnecessary closing parenthesis under /bracketed-paste-begin
> ()/ from section 8.4.3 of /Bash Reference Manual/
Thanks for the report.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vi
There is an unnecessary closing parenthesis under /bracketed-paste-begin
()/ from section 8.4.3 of /Bash Reference Manual/
diff --git a/lib/readline/doc/rluser.texi b/lib/readline/doc/rluser.texi
index 1c9acdc..d42f6f6 100644
--- a/lib/readline/doc/rluser.texi
+++ b/lib/readline/doc/rluser.texi
@
13 matches
Mail list logo
