[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 <eliz@gnu.org>
>
> > Date: Fri, 24 Nov 2017 21:18:36 +0100
> > From: charles@aurox.ch (Charles A. Roelli)
> > CC: monnier@IRO.UMontreal.CA, 17893@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?
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), (continued)
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Eli Zaretskii, 2017/11/20
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Stefan Monnier, 2017/11/20
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Eli Zaretskii, 2017/11/20
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Stefan Monnier, 2017/11/20
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Eli Zaretskii, 2017/11/20
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Andreas Schwab, 2017/11/20
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Charles A. Roelli, 2017/11/20
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Eli Zaretskii, 2017/11/20
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Charles A. Roelli, 2017/11/24
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Eli Zaretskii, 2017/11/24
- bug#17893: 24.4.50; (error "Marker does not point anywhere"),
Charles A. Roelli <=
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Eli Zaretskii, 2017/11/25
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Stefan Monnier, 2017/11/25
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Eli Zaretskii, 2017/11/25
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Andreas Schwab, 2017/11/25
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Eli Zaretskii, 2017/11/25
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Andreas Schwab, 2017/11/25
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), martin rudalics, 2017/11/26
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Eli Zaretskii, 2017/11/26
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), martin rudalics, 2017/11/27
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Andreas Schwab, 2017/11/27