unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 17893@debbugs.gnu.org, "Charles A. Roelli" <charles@aurox.ch>
Subject: bug#17893: 24.4.50; (error "Marker does not point anywhere")
Date: Mon, 20 Nov 2017 11:51:45 -0500	[thread overview]
Message-ID: <jwvpo8csxx5.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <83h8tpdkd4.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 20 Nov 2017 17:45:43 +0200")

> Bother: this is actually the tip of an iceberg.  Buffer local
> variables that get cloned by clone-buffer could hold any number of
> markers pointing into the original buffer.

Indeed.

> E.g., info.el itself maintains a per-buffer marker in
> Info-tag-table-marker; evaluate it after M-n and see what it
> tells you.

And for that reason, clone-buffer runs `clone-buffer-hook`, which
Info-mode uses to do:

    (defun Info-clone-buffer ()
      (when (bufferp Info-tag-table-buffer)
        (setq Info-tag-table-buffer
              (with-current-buffer Info-tag-table-buffer (clone-buffer))))
      (let ((m Info-tag-table-marker))
        (when (markerp m)
          (setq Info-tag-table-marker
                (if (and (marker-position m) (bufferp Info-tag-table-buffer))
                    (with-current-buffer Info-tag-table-buffer
                      (copy-marker (marker-position m)))
                  (make-marker))))))

which I believe DTRT.

> For mark-ring, I think it's easier to just reset it to nil in the new
> clone (it's arguably even more correct, since this is a fresh buffer),

I didn't think about it when I saw Charles's patch, but yes resetting it
to nil would make sense.

> but in general this is a ticking bomb, unless I'm missing something.
> If I'm right, the only solution is to walk all the markers that point
> to the parent buffer and clone them to point to the cloned buffer
> (this has to be done in C).

This can't be done in C because after creating those new markers, where
would we store them?  E.g. cloning all the markers that are in
`mark-ring` would just create new markers but it would fail to create
a new list holding those markers, stored in the new buffer-local value
of `mark-ring` (walking the markers doesn't tell us that they're
referred to from `mark-ring`).

Hence clone-buffer-hook, which doesn't solve the problem in itself, but
makes it possible to fix it manually where needed.


        Stefan





  reply	other threads:[~2017-11-20 16:51 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-01 21:10 bug#17893: 24.4.50; (error "Marker does not point anywhere") Drew Adams
2014-07-01 22:42 ` Stefan Monnier
2014-07-02  1:17   ` Drew Adams
2014-07-02  2:11     ` Stefan Monnier
2014-07-02  2:49       ` Drew Adams
2014-07-02 14:09         ` Stefan Monnier
2014-07-02 14:22           ` Drew Adams
2014-07-02 14:58             ` Stefan Monnier
2014-07-02 16:08               ` Drew Adams
2014-07-02 18:24                 ` Stefan Monnier
2014-07-02 18:39                   ` Drew Adams
2014-07-02 18:58                 ` Stephen Berman
2014-07-15 16:19   ` Drew Adams
2017-11-12 10:41     ` Charles A. Roelli
2017-11-12 21:03       ` Stefan Monnier
2017-11-14 19:56         ` Charles A. Roelli
2017-11-14 20:08           ` Stefan Monnier
2017-11-19 19:31             ` Charles A. Roelli
2017-11-20 15:45               ` Eli Zaretskii
2017-11-20 16:51                 ` Stefan Monnier [this message]
2017-11-20 17:55                   ` Eli Zaretskii
2017-11-20 18:59                     ` Stefan Monnier
2017-11-20 19:32                       ` Eli Zaretskii
2017-11-20 19:49                 ` Andreas Schwab
2017-11-20 20:01                 ` Charles A. Roelli
2017-11-20 20:29                   ` Eli Zaretskii
2017-11-24 20:18                     ` Charles A. Roelli
2017-11-24 20:39                       ` Eli Zaretskii
2017-11-25 14:13                         ` Charles A. Roelli
2017-11-25 16:06                           ` Eli Zaretskii
2017-11-25 16:48                             ` Stefan Monnier
2017-11-25 17:20                               ` Eli Zaretskii
2017-11-25 18:30                             ` Andreas Schwab
2017-11-25 19:23                               ` Eli Zaretskii
2017-11-25 20:47                                 ` Andreas Schwab
2017-11-26 10:26                             ` martin rudalics
2017-11-26 16:07                               ` Eli Zaretskii
2017-11-27  8:50                                 ` martin rudalics
2017-11-27  9:54                                   ` Andreas Schwab
2017-11-27 10:02                                     ` martin rudalics
2017-11-24 21:22                       ` Stefan Monnier

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=jwvpo8csxx5.fsf-monnier+emacsbugs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=17893@debbugs.gnu.org \
    --cc=charles@aurox.ch \
    --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 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).