From: Tassilo Horn <tsdh@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: electric-pair-mode
Date: Fri, 29 Nov 2013 08:01:49 +0100 [thread overview]
Message-ID: <87fvqf1yjm.fsf@thinkpad.tsdh.org> (raw)
In-Reply-To: <jwveh69dyyg.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 21 Nov 2013 20:13:41 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> For example, in all kinds of lisp modes I'm using paredit which
>> provides both features, too, in a slightly different form. So there
>> I wouldn't want to activate these modes (although it seems having
>> them activated doesn't do any harm).
>
> Looks like there's no problem, then.
Ok, now I've found a mode where it's a problem. AUCTeX has its own
TeX-ified brace pairing feature which for example knows that \left( has
to be closed by \right(, \{ by \}, etc. With `electric-pair-mode'
enabled, when typing a { I get two closing braces.
Right now, I have "disabled" `electric-pair-mode' for auctex using:
;; AUCTeX brace pairing feature doesn't play nice with `electric-pair-mode'
;; which is a global minor mode as of emacs 24.4.
(when (and (boundp 'electric-pair-mode)
(boundp 'electric-pair-inhibit-predicate))
(set (make-local-variable 'electric-pair-inhibit-predicate)
(lambda (char) t))))
Is that the way it's supposed to be done?
I somehow have the feeling that `electric-pair-mode' should only do its
magic if the opening paren/brace/bracket is inserted with
`self-insert-command'. For modes that bind ({[ to special commands
(like paredit and auctex), chances are high that you get some
interference with whatever special logic the mode does. On the other
hand, there doesn't seem to be a problem with paredit, so maybe we're
just doing something wrong in auctex...
Bye,
Tassilo
next prev parent reply other threads:[~2013-11-29 7:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-16 23:27 electric-pair-mode Stefan Monnier
2013-11-17 3:10 ` electric-pair-mode Xue Fuqiao
2013-11-17 18:30 ` electric-pair-mode Jorgen Schaefer
2013-11-17 21:12 ` electric-pair-mode Stefan Monnier
2013-11-18 11:04 ` electric-pair-mode Xue Fuqiao
2013-11-17 21:05 ` electric-indent-mode (was: electric-pair-mode) Stefan Monnier
2013-11-19 9:48 ` electric-indent-mode (was electric-pair-mode) Stephen Berman
2013-11-19 13:41 ` Stefan Monnier
2013-11-19 14:39 ` Stephen Berman
2013-11-21 13:48 ` electric-pair-mode Tassilo Horn
2013-11-22 1:13 ` electric-pair-mode Stefan Monnier
2013-11-22 13:20 ` electric-pair-mode Alexander Baier
2013-11-22 19:13 ` electric-pair-mode Tassilo Horn
2013-11-22 20:35 ` electric-pair-mode Alexander Baier
2013-11-22 21:09 ` electric-pair-mode Tassilo Horn
2013-11-23 1:53 ` electric-pair-mode Stefan Monnier
2013-11-29 7:01 ` Tassilo Horn [this message]
2013-11-29 13:44 ` electric-pair-mode Stefan Monnier
2013-11-29 17:10 ` electric-pair-mode Tassilo Horn
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=87fvqf1yjm.fsf@thinkpad.tsdh.org \
--to=tsdh@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).