From: Marcin Borkowski <mbork@mbork.pl>
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: Wed, 15 Jan 2020 19:43:26 +0100 [thread overview]
Message-ID: <87o8v4k1bl.fsf@mbork.pl> (raw)
In-Reply-To: <87sgkpp9ha.fsf@web.de>
On 2020-01-09, at 04:57, Michael Heerdegen <michael_heerdegen@web.de> wrote:
> Marcin Borkowski <mbork@mbork.pl> writes:
>
>> 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.
>
> Just for fun I've created a template for how the least common multiple
> of our expectations could look like. I guess there are many different
> expectations of how contents, visualizations and ways of saving for
> notes could look like, so I made it so that all of that is changeable
> and extensible.
>
> I'm not yet sure what would have to be done to support mass annotation
> from occur buffers since I don't use them a lot.
>
> I'm also not sure where in the implementation I could rely on existing
> code - especially for saving (eieio-persistent maybe?).
Hi Michael,
and thanks for this. (Unfortunately, I could no longer follow the
discussion, because life & time, but I'd really like to catch up.)
This looks quite interesting. Things I'd probably change would be:
highlighting the region instead of the character at point, jumping to
previous/next note, a list of notes, and an overlay showing the text of
the note even without hovering on it. Of course, this would be a major
effort, but I like your PoC.
I'd really like to work on it, but realistically, I won't be able for at
least several months:-(...
Best,
--
Marcin Borkowski
http://mbork.pl
next prev parent reply other threads:[~2020-01-15 18:43 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
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 [this message]
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=87o8v4k1bl.fsf@mbork.pl \
--to=mbork@mbork.pl \
--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).