Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > gnu.bash.bug > #14913 > unrolled thread

Re: Problem with vi mode in bash 5.0 beta

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Problem with vi mode in bash 5.0 beta Chet Ramey <chet.ramey@case.edu> - 2018-12-13 08:54 -0500

#14913 — Re: Problem with vi mode in bash 5.0 beta

On 12/12/18 5:32 PM, Stan Marsh wrote:
> (This is all after doing "set -o vi")
> 
> In previous versions of bash, I could do the following keys: <Esc> / ^ foo <Enter>
> and it would find the most recent command that starts with foo.  This is all as
> expected.
> 
> However, in bash 5.0 beta (self-compiled), this doesn't work. It always leaves the
> cursor line empty (as if there was no matching history line).  If I leave out the ^,
> then it works as expected (but, of course, matches the string anywhere, not just at
> the beginning of the line).

These are fixed in bash-5.0-beta2.

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

[toc] | [standalone]

Back to top | Article view | gnu.bash.bug

csiph-web