From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21824@debbugs.gnu.org
Subject: bug#21824: 25.0.50; overlay modification-hooks called with wrong buffer
Date: Wed, 4 Nov 2015 19:19:27 -0500 [thread overview]
Message-ID: <CAM-tV-_KL0-GAPkFGn4APfrmNWrSSU27hptSeCLB_oYeF-vx4A@mail.gmail.com> (raw)
In-Reply-To: <83611hvl0w.fsf@gnu.org>
On Wed, Nov 4, 2015 at 10:31 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> Thanks. Unfortunately, I don't really have enough time at the moment
> to install all of that, certainly not libclang. Is it okay if I ask
> questions and make observations, and you then try digging into this
> problem, find the answers, and post them here?
Yup, totally understandable.
> I see that yas-global-mode is turned on, which (AFAIU) means yasnippet
> tries to do its thing in every buffer, including *Messages*, right?
>
I can reproduce the problem with yas-minor-mode enabled only in the C++ buffer.
But I *can't* reproduce the problem with highlight-parenthesis-mode
only in the C++ buffer. It seems global-highlight-parenthesis-mode is
required.
> That in turn means every modification of the *Messages* buffer will,
> quite correctly, call yas--on-field-overlay-modification, provided
> that the buffer has overlays in it.
To clarify, yas--on-field-overlay-modification is *only* called as a
modification-hooks property of overlays that yasnippet creates.
Yasnippet never calls it directly.
Yasnippet only creates overlays after expanding a snippet, so this
should never occur in the *Messages* buffer (unless the user decides
to start typing and expanding snippets there). However, there are
several other packages involved.
> After this error happens, what does the following produce if invoked
> with *Messages* being the current buffer:
>
> M-: (overlays-in (point-min) (point-max)) RET
Evaluating in the stackframe where the error is triggered:
(#<overlay from 1 to 1 in *Messages*> #<overlay from 1 to 1 in
*Messages*> #<overlay from 1 to 1 in *Messages*> #<overlay from 1 to 1
in *Messages*> #<overlay from 1 to 1 in *Messages*> #<overlay from 1
to 1 in *Messages*> #<overlay from 1 to 1 in *Messages*> #<overlay
from 1 to 1 in *Messages*>)
Afterwards it gives nil.
The "from 1 to 1" suggests overlays created by highlight-parentheses,
as I see it has a (make-overlay 0 0 nil t) call in a loop.
next prev parent reply other threads:[~2015-11-05 0:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 3:06 bug#21824: 25.0.50; overlay modification-hooks called with wrong buffer Noam Postavsky
2015-11-04 15:31 ` Eli Zaretskii
2015-11-05 0:19 ` Noam Postavsky [this message]
2015-11-05 3:33 ` Noam Postavsky
2015-11-05 16:09 ` Eli Zaretskii
2015-11-06 3:14 ` Noam Postavsky
2015-11-06 15:23 ` Eli Zaretskii
2015-11-06 15:37 ` Eli Zaretskii
2015-11-07 2:24 ` Noam Postavsky
2015-11-07 8:28 ` Eli Zaretskii
2015-11-07 16:22 ` Noam Postavsky
2015-11-07 18:07 ` Eli Zaretskii
2015-11-08 1:43 ` Noam Postavsky
2015-11-08 3:41 ` Eli Zaretskii
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=CAM-tV-_KL0-GAPkFGn4APfrmNWrSSU27hptSeCLB_oYeF-vx4A@mail.gmail.com \
--to=npostavs@users.sourceforge.net \
--cc=21824@debbugs.gnu.org \
--cc=eliz@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.
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.