unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 17893@debbugs.gnu.org, charles@aurox.ch, monnier@IRO.UMontreal.CA
Subject: bug#17893: 24.4.50; (error "Marker does not point anywhere")
Date: Sun, 26 Nov 2017 18:07:40 +0200	[thread overview]
Message-ID: <83d1456n1v.fsf@gnu.org> (raw)
In-Reply-To: <5A1A96D5.7050706@gmx.at> (message from martin rudalics on Sun, 26 Nov 2017 11:26:29 +0100)

> Date: Sun, 26 Nov 2017 11:26:29 +0100
> From: martin rudalics <rudalics@gmx.at>
> CC: 17893@debbugs.gnu.org, monnier@IRO.UMontreal.CA
> 
>  > What is missing is a way of methodically walking all the markers
>  > reachable from the cloned buffer's local variables, and changing each
>  > marker to point to the cloned buffer instead of the parent buffer.
> 
> Have `clone-buffer' record the parent buffer somewhere and when we
> encounter a marker referring a dead buffer that is the same as the
> recorded parent buffer redirect the marker on the fly to the cloned
> buffer.  Not overly clean but what could we lose?

When a buffer is deleted, all the markers that point to it get their
buffer wiped out, so I think the above method cannot work, unless you
replace all NULL buffer pointers with the cloned buffer -- which will
probably be too much.

And remember that markers without any buffer do not get adjusted, so
their position will quickly become incorrect or even outside the
cloned buffer's text, and then such markers will become useless.  So
we cannot delay this until the marker is accessed by some Lisp.





  reply	other threads:[~2017-11-26 16:07 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
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 [this message]
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=83d1456n1v.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=17893@debbugs.gnu.org \
    --cc=charles@aurox.ch \
    --cc=monnier@IRO.UMontreal.CA \
    --cc=rudalics@gmx.at \
    /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).