Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14911
| Path | csiph.com!goblin3!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail |
|---|---|
| From | Stan Marsh <gazelle@xmission.com> |
| Newsgroups | gnu.bash.bug |
| Subject | Problem with vi mode in bash 5.0 beta |
| Date | Wed, 12 Dec 2018 15:32:21 -0700 |
| Lines | 16 |
| Approved | bug-bash@gnu.org |
| Message-ID | <mailman.5651.1544653994.1284.bug-bash@gnu.org> (permalink) |
| NNTP-Posting-Host | lists.gnu.org |
| X-Trace | usenet.stanford.edu 1544653994 27047 208.118.235.17 (12 Dec 2018 22:33:14 GMT) |
| X-Complaints-To | action@cs.stanford.edu |
| To | bash@packages.debian.org, bug-bash@gnu.org |
| Envelope-to | bug-bash@gnu.org |
| X-XM-SPF | eid=1gXD3F-0004dw-Gd; ; ; mid=<E1gXD3F-0005E8-72@shell.xmission.com>; ; ; hst=mx02.mta.xmission.com; ; ; ip=166.70.8.4; ; ; frm=gazelle@xmission.com; ; ; spf=neutral |
| X-SA-Exim-Connect-IP | 166.70.8.4 |
| X-SA-Exim-Mail-From | gazelle@xmission.com |
| X-SA-Exim-Scanned | No (on mx02.mta.xmission.com); SAEximRunCond expanded to false |
| X-detected-operating-system | by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] |
| X-Received-From | 166.70.13.231 |
| X-BeenThere | bug-bash@gnu.org |
| X-Mailman-Version | 2.1.21 |
| Precedence | list |
| List-Id | Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org> |
| List-Unsubscribe | <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe> |
| List-Archive | <http://lists.gnu.org/archive/html/bug-bash/> |
| List-Post | <mailto:bug-bash@gnu.org> |
| List-Help | <mailto:bug-bash-request@gnu.org?subject=help> |
| List-Subscribe | <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe> |
| Xref | csiph.com gnu.bash.bug:14911 |
Show key headers only | View raw
(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). Incidentally, it occurs to me that I could just do: "fc foo" and it would do pretty much the same thing (match only at the beginning), but my fingers are used to doing it the other way.
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Problem with vi mode in bash 5.0 beta Stan Marsh <gazelle@xmission.com> - 2018-12-12 15:32 -0700
csiph-web