From: Drew Adams <drew.adams@oracle.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: RE: Temporary notes in Emacs buffers?
Date: Sun, 5 Jan 2020 09:54:43 -0800 (PST) [thread overview]
Message-ID: <555268d5-76f7-4ed8-90ef-9878551320e7@default> (raw)
In-Reply-To: <87mub2d3x6.fsf@web.de>
> > Vanilla Emacs bookmarks provide the ability to annotate.
> > Bookmark+ enhances annotating (e.g. to use Org and
> > indirection), but the annotation provided by vanilla
> > Emacs bookmarking does what you requested.
(Note: That statement is only about annotating.
Your response is about automatic relocation and
highlighting.)
> Do Vanilla bookmarks really recognize automatically
> when a bookmarked position has changed because the
> user has inserted some preceding text? I mean, I
> know bookmarks save surrounding text to work around that
> problem but that works only by luck most of the time.
Yes. I don't think it works only by luck most of
the time. I think it works well most of the time.
Of course, if there are large edits before the
next time you jump to a bookmark, then, yes, it
might not be possible to relocate it automatically
(in which case you're prompted to relocate it
manually).
But edits between jumps to a bookmark are, I think,
typically not so large as to prevent automatic
relocating.
Also, the automatic relocation of Bookmark+ is
better than that of vanilla Emacs.
> Same question for highlighting bookmarked positions:
> I thought such features were only added by "bookmark+"?
Correct. That is added by Bookmark+. It's not
available with vanilla bookmark handling.
If you use Bookmark+ then the highlighting is
available also for bookmarks created with vanilla
Emacs. But the highlighting is not available
without Bookmark+.
next prev parent reply other threads:[~2020-01-05 17:54 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-27 10:19 Temporary notes in Emacs buffers? Marcin Borkowski
2019-12-27 10:43 ` Mpho Jele
2019-12-27 11:51 ` tomas
2020-01-01 21:48 ` Marcin Borkowski
2019-12-27 15:54 ` Drew Adams
2020-01-02 17:49 ` Marcin Borkowski
2020-01-05 2:37 ` Michael Heerdegen
2020-01-05 17:54 ` Drew Adams [this message]
2020-01-06 5:18 ` Jean-Christophe Helary
2020-01-06 15:12 ` Drew Adams
2020-01-09 1:03 ` Michael Heerdegen
2020-01-09 23:35 ` arthur miller
2020-01-10 4:58 ` Michael Heerdegen
2020-01-10 9:30 ` Robert Pluim
2020-01-10 10:01 ` Michael Heerdegen
2020-01-10 17:04 ` Drew Adams
2020-01-10 9:10 ` Unknown
2019-12-27 17:48 ` Sharon Kimble
2020-01-01 1:42 ` Michael Heerdegen
2020-01-01 4:45 ` Drew Adams
2020-01-01 5:00 ` Michael Heerdegen
2020-01-01 6:25 ` Drew Adams
2020-01-01 20:34 ` John Yates
2020-01-01 21:19 ` Drew Adams
2020-01-01 21:47 ` Marcin Borkowski
2020-01-02 1:25 ` Michael Heerdegen
2020-01-02 3:16 ` Drew Adams
2020-01-02 3:45 ` Michael Heerdegen
2020-01-02 5:30 ` Drew Adams
2020-01-02 15:41 ` Drew Adams
2020-01-03 1:07 ` Michael Heerdegen
2020-01-03 3:35 ` John Yates
2020-01-03 6:38 ` Drew Adams
2020-01-03 7:06 ` Drew Adams
2020-01-04 6:39 ` Michael Heerdegen
2020-01-04 16:04 ` Drew Adams
2020-01-06 14:18 ` John Yates
2020-01-06 14:34 ` tomas
2020-01-06 15:19 ` John Yates
2020-01-06 15:31 ` tomas
2020-01-06 16:28 ` arthur miller
2020-01-03 7:00 ` Drew Adams
2020-01-03 13:31 ` arthur miller
2020-01-05 2:18 ` Michael Heerdegen
2020-01-11 7:36 ` Michael Heerdegen
2020-01-11 10:00 ` Jean-Christophe Helary
2020-01-11 11:38 ` Michael Heerdegen
2020-01-11 16:00 ` Drew Adams
2020-01-11 23:46 ` John Yates
2020-01-12 2:47 ` Drew Adams
2020-01-12 7:31 ` Michael Heerdegen
2020-01-12 16:37 ` Drew Adams
2020-01-14 7:08 ` Michael Heerdegen
2020-01-14 17:32 ` Drew Adams
2020-01-15 23:10 ` Drew Adams
2020-01-02 17:48 ` Marcin Borkowski
2020-01-02 17:48 ` Marcin Borkowski
2020-01-09 3:57 ` Michael Heerdegen
2020-01-15 18:43 ` Marcin Borkowski
2020-01-20 12:40 ` Michael Heerdegen
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=555268d5-76f7-4ed8-90ef-9878551320e7@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
/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.
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).