[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: |
Tue, 14 Nov 2017 20:56:58 +0100 |
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Drew Adams <drew.adams@oracle.com>, 17893@debbugs.gnu.org
> Date: Sun, 12 Nov 2017 16:03:09 -0500
>
> > The error happens when the marker at the head of the mark ring no
> > longer points into a buffer.
>
> Hmm... mark-ring is buffer-local, so the marks in there should all point
> to current-buffer. Can you try and figure out why this is not the case?
I was not careful to make sure that the mark-ring contains valid
markers, so it may be an error in my code. On the other hand, looking
at the definition of `clone-buffer' (which my patch uses), I don't see
anything that would update the markers of the mark-ring in the newly
cloned buffer to point to the new buffer instead of the old one.
Maybe that is also a problem? And it doesn't help that I find my code
incredibly hard to read one month on...
Drew's problem is probably related to clone-buffer, especially seeing
as he saw the issue right after having hit M-n in an Info mode buffer:
M-n runs the command clone-buffer (found in Info-mode-map), which is
an interactive compiled Lisp function in ‘simple.el’.
It is bound to M-n, <menu-bar> <Info> <Clone Info buffer>.
(clone-buffer &optional NEWNAME DISPLAY-FLAG)
Ah, turns out that's how you replicate this bug.
1. C-h i
2. Click/drag a few times in the *info* buffer to set some marks
3. M-n C-x o C-x k RET
4. Click in the remaining *info*<2> buffer:
set-transient-map PCH: (error "Marker does not point anywhere")
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Charles A. Roelli, 2017/11/12
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Stefan Monnier, 2017/11/12
- 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"), Stefan Monnier, 2017/11/14
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Charles A. Roelli, 2017/11/19
- 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