From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: stefan@marxist.se, 36417@debbugs.gnu.org
Subject: bug#36417: [PATCH] Document bookmark annotations in Emacs Manual
Date: Fri, 28 Jun 2019 11:52:42 -0700 (PDT) [thread overview]
Message-ID: <079f4f36-497b-4580-905f-3acb2eb89f3e@default> (raw)
In-Reply-To: <<83mui1h7vf.fsf@gnu.org>>
> > > > Btw, what is the use case for using annotations but not showing them?
> > > > If that use case is not important enough, perhaps we shouldn't mention
> > > > the second option.
> > >
> > > Good point. I don't think it's a very important use case, so I
> > > removed it.
> >
> > It should not be removed.
>
> We didn't remove the variable, we just avoided documenting it in the
> manual.
Yes, I realized that. And that was perhaps based on
Stefan's saying he doesn't think it's a very important
use case.
I pointed out that it is just as important as using
the other option.
> Not every option of every package is documented in the Emacs
> manual.
No, of course not. You always say that, as if
someone claimed the contrary. No one has _ever_
done so, as far I know.
> If you think bookmark.el warrants a more detailed
> documentation, please consider writing a separate Texinfo manual for
> it, as we have for many other packages.
That's reading a lot into my reply. I was setting
the record straight wrt what these variables are
for, and pointing out that neither is more important
than the other. You can document them both in the
manual or remove them both from the manual, as far
as I'm concerned. You can document only one of them,
but there is not special reason (IMHO) to choose this
one or that one.
next prev parent reply other threads:[~2019-06-28 18:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<CADwFkm=Bvo+Y3fjbzLdthQwPsjZ1sS_J4vMqNzp_rzX7DVUKzA@mail.gmail.com>
[not found] ` <<83y31lhjwz.fsf@gnu.org>
2019-06-28 16:01 ` bug#36417: [PATCH] Document bookmark annotations in Emacs Manual Drew Adams
[not found] ` <<CADwFkmm89N1q7SQ0YY++Q=k5pOwZmQhjOs+aAT6BHptwk6eqHA@mail.gmail.com>
[not found] ` <<93a1eeb8-568b-4ecc-9d38-37ac23545977@default>
[not found] ` <<83mui1h7vf.fsf@gnu.org>
2019-06-28 18:52 ` Drew Adams [this message]
2019-06-28 19:45 ` Eli Zaretskii
[not found] <<<CADwFkm=Bvo+Y3fjbzLdthQwPsjZ1sS_J4vMqNzp_rzX7DVUKzA@mail.gmail.com>
[not found] ` <<<83y31lhjwz.fsf@gnu.org>
[not found] ` <<<CADwFkmm89N1q7SQ0YY++Q=k5pOwZmQhjOs+aAT6BHptwk6eqHA@mail.gmail.com>
[not found] ` <<<93a1eeb8-568b-4ecc-9d38-37ac23545977@default>
[not found] ` <<<83mui1h7vf.fsf@gnu.org>
[not found] ` <<079f4f36-497b-4580-905f-3acb2eb89f3e@default>
[not found] ` <<83k1d5h4u9.fsf@gnu.org>
2019-06-28 22:26 ` Drew Adams
2019-06-28 11:51 Stefan Kangas
2019-06-28 14:19 ` Eli Zaretskii
2019-06-28 15:13 ` Stefan Kangas
2019-06-28 15:18 ` Stefan Kangas
2019-06-28 18:37 ` Eli Zaretskii
2019-06-28 16:07 ` Drew Adams
2019-06-28 18:39 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=079f4f36-497b-4580-905f-3acb2eb89f3e@default \
--to=drew.adams@oracle.com \
--cc=36417@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=stefan@marxist.se \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).