From: Noam Postavsky <npostavs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: contovob@tcd.ie, 35273@debbugs.gnu.org, leah@vuxu.org
Subject: bug#35273: "Marker does not point anywhere" when reading next article
Date: Sat, 27 Apr 2019 12:17:25 -0400 [thread overview]
Message-ID: <871s1nqv6y.fsf@gmail.com> (raw)
In-Reply-To: <83zhokabrx.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 20 Apr 2019 19:20:50 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Sat, 20 Apr 2019 16:44:04 +0300
>> From: Eli Zaretskii <eliz@gnu.org>
>> Cc: contovob@tcd.ie, 35273@debbugs.gnu.org, leah@vuxu.org
>>
>> > > I think it would be better to try to understand how we got such an
>> > > overlay. Was it deleted, per chance?
>> >
>> > I entirely agree with this, but how to check for that?
>>
>> But a breakpoint in delete-overlay?
I managed to reproduce (wasn't too hard actually). All the overlay
deletion seems to come from gnus. I got hits from erase-buffer (called
by gnus), gnus-kill-all-overlays, and gnus-cite-delete-overlays.
> Btw, does anyone understand how does elscreen affect this issue? Does
> that package manipulate overlays or help-echo properties?
Unclear. It doesn't have any delete-overlay calls at all. But it does
create and move its own overlay. And it does have a few help-echo
properties.
next prev parent reply other threads:[~2019-04-27 16:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-14 13:42 bug#35273: "Marker does not point anywhere" when reading next article Leah Neukirchen
2019-04-14 16:31 ` Basil L. Contovounesios
2019-04-14 21:19 ` Leah Neukirchen
2019-04-16 12:38 ` Noam Postavsky
2019-04-16 12:50 ` Leah Neukirchen
2019-04-16 13:13 ` Noam Postavsky
2019-04-16 13:21 ` Leah Neukirchen
2019-04-16 13:56 ` Noam Postavsky
2019-04-16 14:04 ` Leah Neukirchen
2019-04-16 15:02 ` Eli Zaretskii
2019-04-20 12:05 ` Noam Postavsky
2019-04-20 13:44 ` Eli Zaretskii
2019-04-20 16:20 ` Eli Zaretskii
2019-04-27 16:17 ` Noam Postavsky [this message]
2019-04-27 16:49 ` Eli Zaretskii
2019-04-27 19:28 ` Noam Postavsky
2019-04-27 19:35 ` Eli Zaretskii
2019-04-28 12:45 ` Noam Postavsky
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=871s1nqv6y.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=35273@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=eliz@gnu.org \
--cc=leah@vuxu.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.