[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#17893: 24.4.50; (error "Marker does not point anywhere")
From: |
Stefan Monnier |
Subject: |
bug#17893: 24.4.50; (error "Marker does not point anywhere") |
Date: |
Fri, 24 Nov 2017 16:22:10 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
>> > By C, do you mean the function `clone-buffer'?
>> No, I meant what's in marker.c.
> I suppose the main issue is fixed in master now:
Indeed.
> 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.
That's just a different hook, with more or less the same downsides as
the one we already have, so I don't see much benefit.
Stefan
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), (continued)
- 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
- 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"),
Stefan Monnier <=