unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Don Woods <don@icynic.com>
To: help-gnu-emacs@gnu.org
Cc: don@icynic.com
Subject: Re: cannot disable paren matching
Date: Tue, 27 Dec 2016 15:35:20 -0700 (MST)	[thread overview]
Message-ID: <201612272235.uBRMZKL1041301@home.icynic.com> (raw)
In-Reply-To: <CAOj2CQQKPHatgqRcmzVTDG2ENk_7hFbEucZugS4FJhH1dB2k6Q@mail.gmail.com>

Thanks John and Skip for the answers so far.  I tried (show-paren-mode -1)
and it seems to be the same as (show-paren-mode 0) in that it yields nil,
whereas (show-paren-mode 1) yields t.  I've also tried M-x show-paren-mode,
which toggles the state.  Interestingly, even in fundamental-mode, turning
show-paren-mode off does NOT stop emacs from briefly moving to the matching
open when I type a close, whether or not I'm in overwrite-mode.

As to John's scenario starting with emacs -Q, I tried it on my emacs and
ended with "a{b}c{d}r}" in the buffer, i.e. with two extra chars at the end
due to the two occurrences of buggy behavior on close.  I have emacs 24.2.1
on another system (unix not Mac, not that that should matter) and it shows
the same bug.  I guess I'll have to see if I can get 25 installed on either
or both of those systems.

Perhaps someone who has Emacs 24 installed can try John's scenario and shed
further light?

	-- Don.



  reply	other threads:[~2016-12-27 22:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-27 20:29 cannot disable paren matching Don Woods
2016-12-27 21:23 ` Skip Montanaro
2016-12-27 21:30 ` John Mastro
2016-12-27 21:52   ` John Mastro
2016-12-27 22:35     ` Don Woods [this message]
2016-12-27 21:36 ` Stefan Monnier
2016-12-27 22:42 ` Konstantin Shakhnov
2016-12-27 23:05   ` John Mastro
2016-12-27 23:14     ` Stefan Monnier
2016-12-28  0:46     ` Don Woods
  -- strict thread matches above, loose matches on Subject: below --
2016-12-27 23:18 martin rudalics

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/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201612272235.uBRMZKL1041301@home.icynic.com \
    --to=don@icynic.com \
    --cc=help-gnu-emacs@gnu.org \
    /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).