Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14913
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: Problem with vi mode in bash 5.0 beta |
| Date | 2018-12-13 08:54 -0500 |
| Organization | ITS, Case Western Reserve University |
| Message-ID | <mailman.5675.1544709303.1284.bug-bash@gnu.org> (permalink) |
| References | <E1gXD3F-0005E8-72@shell.xmission.com> |
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/
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: Problem with vi mode in bash 5.0 beta Chet Ramey <chet.ramey@case.edu> - 2018-12-13 08:54 -0500
csiph-web