From: Mark H Weaver <mhw@netris.org>
To: Daniel Tam <danooo.tam@gmail.com>
Cc: 32501@debbugs.gnu.org
Subject: bug#32501: Bouncing parentheses broken in REPL with vi-mode enabled
Date: Thu, 23 Aug 2018 00:03:09 -0400 [thread overview]
Message-ID: <87lg8xbugy.fsf@netris.org> (raw)
In-Reply-To: <87pny9by7s.fsf@netris.org> (Mark H. Weaver's message of "Wed, 22 Aug 2018 22:42:15 -0400")
Hi again,
> Daniel Tam <danooo.tam@gmail.com> writes:
>
>> I've activated readline support for the Guile repl, but I've found that
>> if my inputrc enables vi-mode, then the bouncing parentheses feature
>> doesn't work. Disabling vi-mode does the trick.
>
> Indeed. For some reason that I cannot determine, the bouncing
> parentheses feature is specifically disabled when the vi keymap is in
> use.
I think I now see the reason for it. I noticed that readline's default
vi keymap includes a binding for '%', which jumps to the paren matching
the one under the cursor. That reminded me, from many years ago when I
used vi more often, that this is the way that old vi traditionally
allows matching parens to be found.
So, I guess the decision long ago to disable bouncing parens when in vi
mode was to match the way that emacs and vi behaved at that time.
However, I just tried modern vim, and I see that it now highlights
matching parens by default. So, we should probably remove the 'if' to
match this newer behavior.
Mark
next prev parent reply other threads:[~2018-08-23 4:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 15:47 bug#32501: Bouncing parentheses broken in REPL with vi-mode enabled Daniel Tam
2018-08-23 2:42 ` Mark H Weaver
2018-08-23 4:03 ` Mark H Weaver [this message]
2018-08-23 16:13 ` John Cowan
2018-08-24 5:36 ` Mark H Weaver
2018-08-24 6:09 ` Mark H Weaver
2018-08-24 12:42 ` Daniel Tam
2018-08-24 22:11 ` Mark H Weaver
2022-07-11 12:20 ` bug#32501: Bug #32501 - " Sean
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lg8xbugy.fsf@netris.org \
--to=mhw@netris.org \
--cc=32501@debbugs.gnu.org \
--cc=danooo.tam@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).