unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: contovob@tcd.ie, 35273@debbugs.gnu.org, leah@vuxu.org
Subject: bug#35273: "Marker does not point anywhere" when reading next article
Date: Tue, 16 Apr 2019 18:02:10 +0300	[thread overview]
Message-ID: <83h8aygfil.fsf@gnu.org> (raw)
In-Reply-To: <87tveyxdd7.fsf@gmail.com> (message from Noam Postavsky on Tue, 16 Apr 2019 09:56:36 -0400)

> From: Noam Postavsky <npostavs@gmail.com>
> Date: Tue, 16 Apr 2019 09:56:36 -0400
> Cc: "Basil L. Contovounesios" <contovob@tcd.ie>, 35273@debbugs.gnu.org
> 
> Oh right, OVERLAY_POSITION calls marker_position.  I think the patch
> below should paper over the problem, but I'm not sure if it's the right
> thing.

I think it would be better to try to understand how we got such an
overlay.  Was it deleted, per chance?





  parent reply	other threads:[~2019-04-16 15:02 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 [this message]
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
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

  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=83h8aygfil.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=35273@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    --cc=leah@vuxu.org \
    --cc=npostavs@gmail.com \
    /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).