GNU bug report logs - #17893
24.4.50; (error "Marker does not point anywhere")

Previous Next

Full log

Message #99 received at 17893 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: charles <at> aurox.ch (Charles A. Roelli)
Cc: 17893 <at> debbugs.gnu.org, monnier <at> IRO.UMontreal.CA
Subject: Re: bug#17893: 24.4.50; (error "Marker does not point anywhere")
Date: Sat, 25 Nov 2017 18:06:46 +0200

> Date: Sat, 25 Nov 2017 15:13:08 +0100
> From: charles <at> aurox.ch (Charles A. Roelli)
> CC: monnier <at> IRO.UMontreal.CA, 17893 <at> debbugs.gnu.org
> 
> > > To solve the problem more generally, maybe clone-buffer could look for
> > > local variables with a non-nil symbol property (called, say,
> > > `clone-buffer-update-function'), the value of which would be a
> > > function that updates the "cloned" variable properly.
> > 
> > This is not different from running a clone-buffer-update-function: it
> > again lets modes take care of the variables thy know about which need
> > special handling at clone time.  My problem with that is that I don't
> > believe this is a complete solution.
> 
> Can you say what you think is missing?

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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.