From: npostavs@users.sourceforge.net
To: Eli Zaretskii <eliz@gnu.org>
Cc: 4854@debbugs.gnu.org, stephen.berman@gmx.net
Subject: bug#4854: 23.1.50; before-string overlay and show-paren-mode
Date: Sun, 03 Jul 2016 11:58:16 -0400 [thread overview]
Message-ID: <871t3ag1d3.fsf@users.sourceforge.net> (raw)
In-Reply-To: <83d1muramh.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 03 Jul 2016 18:42:46 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: npostavs@users.sourceforge.net
>> Date: Sun, 03 Jul 2016 11:36:01 -0400
>> Cc: 4854@debbugs.gnu.org
>>
>> Well, it's possible to avoid moving overlays to minibuffer, but then
>> show-paren-mode stops working in the minibuffer, which I don't think is
>> so great.
>
> To say the least. Please don't, I edit expressions in the minibuffer
> quite a lot, and find show-paren invaluable in general and there in
> particular.
Don't worry, I wasn't intending to. That patch was just for
demonstration. I suppose it might be possible to have paren overlay
per-buffer, so that the overlay doesn't disappear and reappear all the
time, but I don't think it's worth the complication. I'm pretty sure it
would remain possible to write a command that's able to observe some
inconsistencies regardless: since show-paren-mode relies on idle-timers,
the behaviour is affected by the timing of the user's keystrokes. It's
best to write commands that are oblivious to what show-paren-mode does
(e.g., the (cl-some ...) condition I posted in that same message).
next prev parent reply other threads:[~2016-07-03 15:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 14:49 bug#4854: 23.1.50; before-string overlay and show-paren-mode Stephen Berman
2009-11-04 23:08 ` Stephen Berman
2016-07-01 18:42 ` npostavs
2016-07-03 14:33 ` Stephen Berman
2016-07-03 15:36 ` npostavs
2016-07-03 15:42 ` Eli Zaretskii
2016-07-03 15:58 ` npostavs [this message]
2016-07-03 22:23 ` Stephen Berman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871t3ag1d3.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=4854@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=stephen.berman@gmx.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.