From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: martin rudalics <rudalics@gmx.at>
Cc: 349@emacsbugs.donarmstrong.com, bug-gnu-emacs@gnu.org,
Kevin Ryde <user42@zip.com.au>
Subject: bug#349: show-paren-mode overlay extending onto new text
Date: Mon, 02 Jun 2008 09:47:54 -0400 [thread overview]
Message-ID: <jwviqwsvtq5.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <484391EC.2050905@gmx.at> (martin rudalics's message of "Mon, 02 Jun 2008 08:23:40 +0200")
>> I wondered if the make-overlay in show-paren-function
>> might have the "rear-advance" arg nil, unless there's ever a time it
>> ought to extend.
>>
>> In GNU Emacs 22.2.1 (i486-pc-linux-gnu, GTK+ Version 2.12.9)
> [...]
>> show-paren-mode: t
> [...]
> Version 1.75 of paren.el has
> (setq show-paren-overlay-1 (make-overlay from to nil t)))
> and
> (setq show-paren-overlay (make-overlay from to nil t))))
> hence both overlays seem to have "rear-advance" nil.
Indeed, the problem is that compile.el uses insert-before-markers.
So no amount of rear-advance will help.
I have been using a simple patch which adds a buffer-local variable
which I called `window-marker-insertion-type' (but I realize now it
should rather be `window-point-insertion-type'), so major modes can set
this variable if they want `window-point' to be "move after insertion".
This way, compile.el (and other similar packages) might not need to use
insert-before-markers.
Stefan
next prev parent reply other threads:[~2008-06-02 13:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <jwvskvltgb2.fsf-monnier+emacsbugreports@gnu.org>
2008-06-02 1:46 ` bug#349: show-paren-mode overlay extending onto new text Kevin Ryde
2008-06-02 6:23 ` martin rudalics
2008-06-02 13:47 ` Stefan Monnier [this message]
2008-06-03 1:00 ` Kevin Ryde
2008-06-10 16:25 ` bug#349: marked as done (show-paren-mode overlay extending onto new text) Emacs bug Tracking System
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=jwviqwsvtq5.fsf-monnier+emacsbugreports@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=349@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=rudalics@gmx.at \
--cc=user42@zip.com.au \
/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.