From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 17893@debbugs.gnu.org, charles@aurox.ch
Subject: bug#17893: 24.4.50; (error "Marker does not point anywhere")
Date: Mon, 20 Nov 2017 21:32:13 +0200 [thread overview]
Message-ID: <83shd8d9vm.fsf@gnu.org> (raw)
In-Reply-To: <jwv3758ssei.fsf-monnier+emacsbugs@gnu.org> (message from Stefan Monnier on Mon, 20 Nov 2017 13:59:12 -0500)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: charles@aurox.ch, 17893@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.
next prev parent reply other threads:[~2017-11-20 19:32 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 21:10 bug#17893: 24.4.50; (error "Marker does not point anywhere") Drew Adams
2014-07-01 22:42 ` Stefan Monnier
2014-07-02 1:17 ` Drew Adams
2014-07-02 2:11 ` Stefan Monnier
2014-07-02 2:49 ` Drew Adams
2014-07-02 14:09 ` Stefan Monnier
2014-07-02 14:22 ` Drew Adams
2014-07-02 14:58 ` Stefan Monnier
2014-07-02 16:08 ` Drew Adams
2014-07-02 18:24 ` Stefan Monnier
2014-07-02 18:39 ` Drew Adams
2014-07-02 18:58 ` Stephen Berman
2014-07-15 16:19 ` Drew Adams
2017-11-12 10:41 ` Charles A. Roelli
2017-11-12 21:03 ` Stefan Monnier
2017-11-14 19:56 ` Charles A. Roelli
2017-11-14 20:08 ` Stefan Monnier
2017-11-19 19:31 ` Charles A. Roelli
2017-11-20 15:45 ` Eli Zaretskii
2017-11-20 16:51 ` Stefan Monnier
2017-11-20 17:55 ` Eli Zaretskii
2017-11-20 18:59 ` Stefan Monnier
2017-11-20 19:32 ` Eli Zaretskii [this message]
2017-11-20 19:49 ` Andreas Schwab
2017-11-20 20:01 ` Charles A. Roelli
2017-11-20 20:29 ` Eli Zaretskii
2017-11-24 20:18 ` Charles A. Roelli
2017-11-24 20:39 ` Eli Zaretskii
2017-11-25 14:13 ` Charles A. Roelli
2017-11-25 16:06 ` Eli Zaretskii
2017-11-25 16:48 ` Stefan Monnier
2017-11-25 17:20 ` Eli Zaretskii
2017-11-25 18:30 ` Andreas Schwab
2017-11-25 19:23 ` Eli Zaretskii
2017-11-25 20:47 ` Andreas Schwab
2017-11-26 10:26 ` martin rudalics
2017-11-26 16:07 ` Eli Zaretskii
2017-11-27 8:50 ` martin rudalics
2017-11-27 9:54 ` Andreas Schwab
2017-11-27 10:02 ` martin rudalics
2017-11-24 21:22 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83shd8d9vm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=17893@debbugs.gnu.org \
--cc=charles@aurox.ch \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.