Re: Problem with reverse-i-search in 5.1.0(1)-rc1

[Chet Ramey]

On 11/5/20 9:13 AM, Detlef Vollmann wrote:
> On 11/5/20 3:01 PM, Chet Ramey wrote:
>> On 11/5/20 3:12 AM, Detlef Vollmann wrote:
>>> On 11/4/20 9:06 PM, Detlef Vollmann wrote:
 What I don't understand yet is the highlighting.
 Sometimes (but rarely) I see the matched string highlighted
 (actually only starting with the second character).
 But most of the time nothing is highlighted while doing
 reverse-i-search.
>>> Sorry, it's as mentioned before:
>>> I have "set enable-bracketed-paste Off" in my .inputrc.
>>> So no highlighting as expected.
>>
>> Try it with bash-5.1-rc2.
> I did.
> What I'm seeing is no highlighting with "set enable-bracketed-paste Off"
> Should have anything changed here?

That's what should happen. There were cases in bash-5.1-rc1 where
incremental search results would be highlighted even when bracketed paste
was disabled.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRUc...@case.eduhttp://tiswww.cwru.edu/~chet/

Re: Problem with reverse-i-search in 5.1.0(1)-rc1

[Detlef Vollmann]

On 11/5/20 3:01 PM, Chet Ramey wrote:

On 11/5/20 3:12 AM, Detlef Vollmann wrote:

On 11/4/20 9:06 PM, Detlef Vollmann wrote:

What I don't understand yet is the highlighting.
Sometimes (but rarely) I see the matched string highlighted
(actually only starting with the second character).
But most of the time nothing is highlighted while doing
reverse-i-search.

Sorry, it's as mentioned before:
I have "set enable-bracketed-paste Off" in my .inputrc.
So no highlighting as expected.


Try it with bash-5.1-rc2.

I did.
What I'm seeing is no highlighting with "set enable-bracketed-paste Off"
Should have anything changed here?

  Detlef

Re: Problem with reverse-i-search in 5.1.0(1)-rc1

[Chet Ramey]

On 11/5/20 3:12 AM, Detlef Vollmann wrote:
> On 11/4/20 9:06 PM, Detlef Vollmann wrote:
>> What I don't understand yet is the highlighting.
>> Sometimes (but rarely) I see the matched string highlighted
>> (actually only starting with the second character).
>> But most of the time nothing is highlighted while doing
>> reverse-i-search.
> Sorry, it's as mentioned before:
> I have "set enable-bracketed-paste Off" in my .inputrc.
> So no highlighting as expected.

Try it with bash-5.1-rc2.

Chet
-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRUc...@case.eduhttp://tiswww.cwru.edu/~chet/

Re: Problem with reverse-i-search in 5.1.0(1)-rc1

[Detlef Vollmann]

On 11/5/20 9:39 AM, Lawrence Velázquez wrote:

On Nov 5, 2020, at 3:12 AM, Detlef Vollmann  wrote:

BTW, I found no way to set a readline variable from the
command line w/o an external file.
$ echo "set enable-bracketed-paste On" | bind -f -
didn't work.


bind 'set enable-bracketed-paste On'

Thanks!
  Detlef

Re: Problem with reverse-i-search in 5.1.0(1)-rc1

[Lawrence Velázquez]

> On Nov 5, 2020, at 3:12 AM, Detlef Vollmann  wrote:
> 
> BTW, I found no way to set a readline variable from the
> command line w/o an external file.
> $ echo "set enable-bracketed-paste On" | bind -f -
> didn't work.

bind 'set enable-bracketed-paste On'

--
vq

Re: Problem with reverse-i-search in 5.1.0(1)-rc1

[Detlef Vollmann]

On 11/4/20 9:06 PM, Detlef Vollmann wrote:

What I don't understand yet is the highlighting.
Sometimes (but rarely) I see the matched string highlighted
(actually only starting with the second character).
But most of the time nothing is highlighted while doing
reverse-i-search.

Sorry, it's as mentioned before:
I have "set enable-bracketed-paste Off" in my .inputrc.
So no highlighting as expected.

BTW, I found no way to set a readline variable from the
command line w/o an external file.
$ echo "set enable-bracketed-paste On" | bind -f -
didn't work.

  Detlef

Re: Problem with reverse-i-search in 5.1.0(1)-rc1

[Detlef Vollmann]

On 11/2/20 3:34 PM, Chet Ramey wrote:

On 11/2/20 9:17 AM, Detlef Vollmann wrote:


BTW, if you want me to check it you could send me a patch or push
a commit to git.savannah.gnu.org/git/bash.


It will be in the next devel branch push.

Thanks.
I tested it and it works nicely again :-)

What I don't understand yet is the highlighting.
Sometimes (but rarely) I see the matched string highlighted
(actually only starting with the second character).
But most of the time nothing is highlighted while doing
reverse-i-search.
I don't really care, but I have a feeling that something in
my setup is wrong so any hints where to look are welcome.

Thanks again,
  Detlef

Re: Problem with reverse-i-search in 5.1.0(1)-rc1

[Chet Ramey]

On 11/2/20 9:17 AM, Detlef Vollmann wrote:

> BTW, if you want me to check it you could send me a patch or push
> a commit to git.savannah.gnu.org/git/bash.

It will be in the next devel branch push.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRUc...@case.eduhttp://tiswww.cwru.edu/~chet/

Re: Problem with reverse-i-search in 5.1.0(1)-rc1

[Detlef Vollmann]

On 11/1/20 8:58 PM, Chet Ramey wrote:

On 10/31/20 11:00 AM, Detlef Vollmann wrote:

Hello,

since Bash-5.1-rc1  doesn't work for me as previously.
I have the following entries in my history:
man a
man b

Now I type ' m a n' and get:
(reverse-i-search)`man': man b

Now I type '' again.
What I would expect (and what I got with 5.0) is:
(reverse-i-search)`man': man a

Instead I get
(reverse-i-search)`': man b

Note the empty search string.


Thanks for the report. It's not easy to reproduce, and, as you later note,
requires the `C' or `POSIX' locales and things to be done in a certain
order, but I believe I was able to track it down. It will be fixed in
bash-5.1-rc2.


Thanks,
  Detlef

BTW, if you want me to check it you could send me a patch or push
a commit to git.savannah.gnu.org/git/bash.

Re: Problem with reverse-i-search in 5.1.0(1)-rc1

[Chet Ramey]

On 10/31/20 11:00 AM, Detlef Vollmann wrote:
> Hello,
> 
> since Bash-5.1-rc1  doesn't work for me as previously.
> I have the following entries in my history:
> man a
> man b
> 
> Now I type ' m a n' and get:
> (reverse-i-search)`man': man b
> 
> Now I type '' again.
> What I would expect (and what I got with 5.0) is:
> (reverse-i-search)`man': man a
> 
> Instead I get
> (reverse-i-search)`': man b
> 
> Note the empty search string.

Thanks for the report. It's not easy to reproduce, and, as you later note,
requires the `C' or `POSIX' locales and things to be done in a certain
order, but I believe I was able to track it down. It will be fixed in
bash-5.1-rc2.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRUc...@case.eduhttp://tiswww.cwru.edu/~chet/

Re: Problem with reverse-i-search in 5.1.0(1)-rc1

[Detlef Vollmann]

On 10/31/20 4:00 PM, Detlef Vollmann wrote:

Hello,

since Bash-5.1-rc1  doesn't work for me as previously.
I have the following entries in my history:
man a
man b

Now I type ' m a n' and get:
(reverse-i-search)`man': man b

Now I type '' again.
What I would expect (and what I got with 5.0) is:
(reverse-i-search)`man': man a

Instead I get
(reverse-i-search)`': man b

Note the empty search string.
I can type '' as often as I want, but always get the same
result.
I can type the same search string again and will stay at 'man b'.

If I now type '' to cancel the search, I get my prompt
and then still 'man b'.

If I never type '' a second time, '' works
properly (my prompt, but no command).

If I get the empty search string, I can also type a different
search string and reverse-i-search will show me a correct
match or a failure message.  If I now cancel with '',
I still get 'man b', even if a different command was shown
in the failure message.

I've tested this with the Debian package bash 5.1~rc1-2 and a
self-compiled version, no difference.

I've tested this with a test user that has no .bash*, .profile,
.inputrc, also no difference.

I've tested this on xterm, lxterminal and the Linux console
(i.e. no X11).  The only difference was that on the Linux
console the matched part of the command was highlighted.
I didn't see any highlighting in xterm.

My system is a Debian Sid, bash version string is
GNU bash, version 5.1.0(1)-rc1 (x86_64-pc-linux-gnu)

This seems the same problem as described here:
,
except thai I normally don't see highlighting.

If you need any more information, please ask.


Ok, I could narrow it down.
I'm one of those dinasaurs who still prefer the POSIX locale.
If I run 'LANG=en_US.utf8 bash'  works as expected.
(Some other things break, but that's a different story...)

So you should be able to reproduce the problem using
'LANG=POSIX bash'.

HTH,
  Detlef

Problem with reverse-i-search in 5.1.0(1)-rc1

[Detlef Vollmann]

Hello,

since Bash-5.1-rc1  doesn't work for me as previously.
I have the following entries in my history:
man a
man b

Now I type ' m a n' and get:
(reverse-i-search)`man': man b

Now I type '' again.
What I would expect (and what I got with 5.0) is:
(reverse-i-search)`man': man a

Instead I get
(reverse-i-search)`': man b

Note the empty search string.
I can type '' as often as I want, but always get the same
result.
I can type the same search string again and will stay at 'man b'.

If I now type '' to cancel the search, I get my prompt
and then still 'man b'.

If I never type '' a second time, '' works
properly (my prompt, but no command).

If I get the empty search string, I can also type a different
search string and reverse-i-search will show me a correct
match or a failure message.  If I now cancel with '',
I still get 'man b', even if a different command was shown
in the failure message.

I've tested this with the Debian package bash 5.1~rc1-2 and a
self-compiled version, no difference.

I've tested this with a test user that has no .bash*, .profile,
.inputrc, also no difference.

I've tested this on xterm, lxterminal and the Linux console
(i.e. no X11).  The only difference was that on the Linux
console the matched part of the command was highlighted.
I didn't see any highlighting in xterm.

My system is a Debian Sid, bash version string is
GNU bash, version 5.1.0(1)-rc1 (x86_64-pc-linux-gnu)

This seems the same problem as described here:
,
except thai I normally don't see highlighting.

If you need any more information, please ask.

  Detlef