From: Drew Adams <drew.adams@oracle.com>
To: Marcin Borkowski <mbork@mbork.pl>,
Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: RE: Temporary notes in Emacs buffers?
Date: Fri, 27 Dec 2019 07:54:43 -0800 (PST) [thread overview]
Message-ID: <d94bf524-76a6-497f-94b0-0b786a224aff@default> (raw)
In-Reply-To: <87zhfecbpt.fsf@mbork.pl>
> I've been wondering if there is some package which could let me make
> "temporary notes" in Emacs buffers, similar to (but different than) the
> "yellow notes" in some pdf viewers.
>
> My use case is that I'm making a sweeping change across a pretty large
> codebase, and I'd like to make some notes in places I've already
> visited
> / ones I need to change / etc.
>
> At present, I use normal code comments, however, this is suboptimal,
> since I cannot use them in certain modes (occur buffer, JSON).
>
> Ideally, a place with a comment would have that comment highlighted
> somehow, and I should be able to go to the next/previous comment, and
> list all comments in a file or in the project (think Git repo,
> Projectile project or a directory tree). Also, mass inserting such
> comments from an occur/multi-occur/projectile-ag/counsel-rg/etc.
> buffers
> would be great.
>
> What I /don't/ want is modifying the files - the comments might persist
> in some /other/, .gitignore-d file, or just disappear on exiting Emacs.
>
> I know bookmark+ has similar features, but I'd prefer something more
> lightweight.
>
> Does there exist something like that? Am I the only one interested in
> such a feature? (I'd be happy to code it myself, though it would take
> time, of course.)
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.
next prev parent reply other threads:[~2019-12-27 15: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 [this message]
2020-01-02 17:49 ` Marcin Borkowski
2020-01-05 2:37 ` Michael Heerdegen
2020-01-05 17:54 ` Drew Adams
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=d94bf524-76a6-497f-94b0-0b786a224aff@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=mbork@mbork.pl \
/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).