[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#17893: 24.4.50; (error "Marker does not point anywhere")

From: Charles A. Roelli
Subject: 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 <address@hidden>
> > Date: Fri, 24 Nov 2017 21:18:36 +0100
> > From: address@hidden (Charles A. Roelli)
> > CC: address@hidden, address@hidden
> > 
> > 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?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]