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

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: 17893 <at> debbugs.gnu.org, charles <at> aurox.ch
Subject: bug#17893: 24.4.50; (error "Marker does not point anywhere")
Date: Mon, 20 Nov 2017 21:32:13 +0200

> From: Stefan Monnier <monnier <at> iro.umontreal.ca>
> Cc: charles <at> aurox.ch,  17893 <at> debbugs.gnu.org
> Date: Mon, 20 Nov 2017 13:59:12 -0500
> 
> >  M-n
> >  M-: Info-tag-table-marker RET
> >   => #<marker in no buffer>
> 
> Maybe there's a bug, indeed.  Does the above lead to undesired behavior?

I didn't dig deep enough to find out.  But it's clear that such a
marker is useless at best.

> No.  It just assumes that whichever package owns a marker that needs
> special treatment should register itself on that hook.  Maybe that's too
> much to ask, but it's definitely not "impossible".

Registering a hook is easy, the problem is doing everything that's
needed in the hook.  Especially given that clone-buffer is not
documented, and therefore all these caveats are nowhere to be learned.

> > As another data point, there are 6 users of clone-buffer in Emacs
> > core, and only one of them bothers to set up a clone-buffer-hook.
> 
> Do these suffer from problems?

I don't know.  But markers are quite common, so I'd be surprised if
they didn't.

Previous Next

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