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

Previous Next

Full log

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

From: charles <at> aurox.ch (Charles A. Roelli)
To: Eli Zaretskii <eliz <at> gnu.org>
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 15:13:08 +0100

> Date: Fri, 24 Nov 2017 22:39:37 +0200
> From: Eli Zaretskii <eliz <at> gnu.org>
> 
> > Date: Fri, 24 Nov 2017 21:18:36 +0100
> > From: charles <at> aurox.ch (Charles A. Roelli)
> > CC: monnier <at> IRO.UMontreal.CA, 17893 <at> debbugs.gnu.org
> > 
> > I suppose the main issue is fixed in master now:
> 
> That's just one particular case of a more general problem with markers
> stored or referenced from local variables of the cloned buffer.
> 
> > 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?

Previous Next

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