From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Stefan Kangas <stefan@marxist.se>
Cc: 36417@debbugs.gnu.org
Subject: bug#36417: [PATCH] Document bookmark annotations in Emacs Manual
Date: Fri, 28 Jun 2019 09:01:20 -0700 (PDT) [thread overview]
Message-ID: <7a905121-f6ff-429c-b781-7ff38863aa30@default> (raw)
In-Reply-To: <<83y31lhjwz.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.
Showing a bookmark's annotation means displaying
it (in its own buffer).
Option `bookmark-automatically-show-annotations'
is about _automatically_ showing annotations
whenever bookmarks are jumped to. If it is nil
then a bookmark's annotation is shown (displayed)
only on demand.
Option `bookmark-use-annotations" non-nil means
that a buffer is opened for you to add an
annotation, if none exists, or edit an existing
annotation, whenever a bookmark is set.
One is about showing annotations when bookmarks
are jumped to. The other is about editing (and
creating) annotations whenever bookmarks are set
(created or updated).
It is true that the doc string for
`bookmark-use-annotations' mistakenly currently
says `saving' instead of `setting'. That, at
least, should be corrected.
next parent reply other threads:[~2019-06-28 16:01 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 ` Drew Adams [this message]
[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 ` bug#36417: [PATCH] Document bookmark annotations in Emacs Manual Drew Adams
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=7a905121-f6ff-429c-b781-7ff38863aa30@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).