From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: John Cowan Newsgroups: gmane.lisp.guile.bugs Subject: bug#32501: Bouncing parentheses broken in REPL with vi-mode enabled Date: Thu, 23 Aug 2018 12:13:57 -0400 Message-ID: References: <0290e793-0acc-31ed-1d7e-61ed65b9bcf2@gmail.com> <87pny9by7s.fsf@netris.org> <87lg8xbugy.fsf@netris.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000007a14bc05741c8c68" X-Trace: blaine.gmane.org 1535041331 30582 195.159.176.226 (23 Aug 2018 16:22:11 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 23 Aug 2018 16:22:11 +0000 (UTC) Cc: danooo.tam@gmail.com, 32501@debbugs.gnu.org To: Mark H Weaver Original-X-From: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Thu Aug 23 18:22:06 2018 Return-path: Envelope-to: guile-bugs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fssN4-0007o7-6q for guile-bugs@m.gmane.org; Thu, 23 Aug 2018 18:22:06 +0200 Original-Received: from localhost ([::1]:37662 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fssPA-0003CX-MY for guile-bugs@m.gmane.org; Thu, 23 Aug 2018 12:24:16 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:55603) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fssP1-0003Ag-B7 for bug-guile@gnu.org; Thu, 23 Aug 2018 12:24:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fssOx-0003He-5X for bug-guile@gnu.org; Thu, 23 Aug 2018 12:24:07 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:54041) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fssOx-0003Ha-0P for bug-guile@gnu.org; Thu, 23 Aug 2018 12:24:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fssOw-0000EO-SL for bug-guile@gnu.org; Thu, 23 Aug 2018 12:24:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: John Cowan Original-Sender: "Debbugs-submit" Resent-CC: bug-guile@gnu.org Resent-Date: Thu, 23 Aug 2018 16:24:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 32501 X-GNU-PR-Package: guile X-GNU-PR-Keywords: Original-Received: via spool by 32501-submit@debbugs.gnu.org id=B32501.1535041417844 (code B ref 32501); Thu, 23 Aug 2018 16:24:02 +0000 Original-Received: (at 32501) by debbugs.gnu.org; 23 Aug 2018 16:23:37 +0000 Original-Received: from localhost ([127.0.0.1]:59058 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fssOW-0000DW-Ru for submit@debbugs.gnu.org; Thu, 23 Aug 2018 12:23:37 -0400 Original-Received: from mail-wm0-f44.google.com ([74.125.82.44]:39245) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fssFR-0008Qq-WB for 32501@debbugs.gnu.org; Thu, 23 Aug 2018 12:14:14 -0400 Original-Received: by mail-wm0-f44.google.com with SMTP id q8-v6so6444063wmq.4 for <32501@debbugs.gnu.org>; Thu, 23 Aug 2018 09:14:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ccil-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Ggctz6s7rGUzdgdHOU1oAMqgYcnwk9F9mMQyXXIaLHQ=; b=sVoSSi3iDT91r/RJ+h+HBnmiP2QnLPqvUyvN0yFV1SUjALQfWZk0Zf4XeuhIR7pk3a i6Pdr8mlJzqGLfva4p0M3Y4/cUimG5ZzMo2i3YLJO7w2JtIGzBtKlS1o50y8MnpVWm64 p9enEP8AmQJC5ppmxB0zlKqsNLTv7r72RJtBwuclA9U+xDCvvG9cN2cdh+FBX8wUaixO xmfHAQlggmvSgvUrAwStVl9Uut+C2nXNsHfIBMY5oqXUGSoLKoT+2IEDVVidfgc91i4C 4K26DRBn3yNadsA+1YJexQsofduYpGnZJhjeKVqXdc75mJAa4HMMFtxa8aQeh14W8HkX LkFw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Ggctz6s7rGUzdgdHOU1oAMqgYcnwk9F9mMQyXXIaLHQ=; b=GUnbHHsSGLnTYI1mXT55BLvl9ObFSDZ+rYtX94jKF/WU9jVRtNkPkze2Cd+iH3uaLu wTxWLPvPytxcY7AsrcJq5RARUdWe/834eoZVaXEnaapmjRZA+MXYsiXfTUgSl67nc+qQ 6uPp7XLIxfGc5OBuzt/EpU5lXhKLvgvsQYZafDoSrKPmAXDPDjjTujI7D4q0BuX5RqXV 6t2AFr6/vx3gDfhZyEanyfP3gKzhtNkrdt2i7w/P19b/l9EqULG3pKH7mvzRycvObZ00 kcMxkjqPUpwKC9FQFActmi+OIbHruDfyLEkMfnbSNGxN5ESzkBhb3n4roenQHDysfLB8 Mm3A== X-Gm-Message-State: APzg51DSxPlXrn97cidkMo9FXky/uT/YGCC3+7Q5+mDeWlBBlj6PsLLB QzXzhJyuaVwczWwajGRQK6woRY1koT79kYgi2elPEw== X-Google-Smtp-Source: ANB0VdY5ktTJPyMji9FFLyKRqlhGGyqKlPPO58q4Ui6TZB+qQe+fow0TYpgB6ADChKLRy3nHmOGITGlXgNmDF6w5TVM= X-Received: by 2002:a1c:b143:: with SMTP id a64-v6mr6136620wmf.114.1535040848261; Thu, 23 Aug 2018 09:14:08 -0700 (PDT) In-Reply-To: <87lg8xbugy.fsf@netris.org> X-Mailman-Approved-At: Thu, 23 Aug 2018 12:23:35 -0400 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-guile@gnu.org List-Id: "Bug reports for GUILE, GNU's Ubiquitous Extension Language" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Original-Sender: "bug-guile" Xref: news.gmane.org gmane.lisp.guile.bugs:9130 Archived-At: --0000000000007a14bc05741c8c68 Content-Type: text/plain; charset="UTF-8" Indeed, I pretty much only go into vi-mode in vi itself to use %; the rest of the time, I remain an "ex" troglodyte whose only vi-commands are h, j, k, l (and arrow analogues), x, %, and most importantly gQ. Yes, even when writing Lisp. On Thu, Aug 23, 2018 at 12:05 AM Mark H Weaver wrote: > Hi again, > > > Daniel Tam 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 > > > > --0000000000007a14bc05741c8c68 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Indeed, I pretty much only go into vi-mode in vi itself to= use %; the rest of the time, I remain an "ex" troglodyte whose o= nly vi-commands are h, j, k, l (and arrow analogues), x, %, and most import= antly gQ.=C2=A0 Yes, even when writing Lisp.

On Thu, Aug 23, 2018 at 12:05 AM Mark H Weaver <<= a href=3D"mailto:mhw@netris.org" target=3D"_blank">mhw@netris.org> w= rote:
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 featu= re
>> doesn't work. Disabling vi-mode does the trick.
>
> Indeed.=C2=A0 For some reason that I cannot determine, the bouncing > parentheses feature is specifically disabled when the vi keymap is in<= br> > use.

I think I now see the reason for it.=C2=A0 I noticed that readline's de= fault
vi keymap includes a binding for '%', which jumps to the paren matc= hing
the one under the cursor.=C2=A0 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.=C2=A0 So, we should probably remove the 'if= ' to
match this newer behavior.

=C2=A0 =C2=A0 =C2=A0 =C2=A0Mark



--0000000000007a14bc05741c8c68--