unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Gnus: Thread notes?
Date: Fri, 13 Oct 2017 04:21:33 +0200	[thread overview]
Message-ID: <874lr3pz2q.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 87o9pc359b.fsf@web.de

Michael Heerdegen <michael_heerdegen@web.de> writes:

> Hi,
>
> do you know the problem that after some time, you have forgotten which
> messages of a thread were important, and what you wanted to do after
> some consent has been made?
>
> I would like a simple feature in Gnus that could be described as "Thread
> notes": when I click on a message, a file (maybe org) opens, maybe with
> a link back to that message (the file itself would be attached to the
> thread) where you could store some notes about the thread.  When you
> later need to reconsider that thread, that file would serve as a summary
> of the aspects that were important to you, with links to the messages
> and text passages, so you spare the time to re-read the whole thread and
> find the passages yourself.
>
> Is something like that already possible, with means of Gnus or Org, that
> is similarly convenient?  I'm not a heavy org-mode user, so I would
> prefer a solution that is build up on Gnus instead of Org.
>
> Or do people have other interesting workflows that are worth sharing
> helping with that kind of problem?

I'll add a brief shameless plug for my package Gnorb (in Elpa) which
does something like this. Basically you can attach Gnus messages to an
Org heading (using the registry), and jump from the heading to an
ephemeral group holding all the related messages. Plus a bunch of other stuff.




  parent reply	other threads:[~2017-10-13  2:21 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-12 12:44 Gnus: Thread notes? Michael Heerdegen
2017-10-12 12:56 ` Danny YUE
2017-10-12 16:36 ` Göktuğ Kayaalp
2017-10-12 19:25   ` Robert Pluim
2017-10-13  2:21 ` Eric Abrahamsen [this message]
2017-10-16 19:33   ` Michael Heerdegen
2017-10-16 20:14     ` Eric Abrahamsen
2017-10-18 12:18       ` Michael Heerdegen
2017-10-18 14:53         ` Eric Abrahamsen
2017-11-25  2:42       ` Michael Heerdegen
2017-11-25  6:35         ` Eric Abrahamsen
2017-11-26  5:30           ` Michael Heerdegen
2017-11-28  2:19             ` Eric Abrahamsen
2017-11-28  6:02               ` Michael Heerdegen
2017-11-28 16:44                 ` Eric Abrahamsen
2017-11-29  8:10                   ` Michael Heerdegen
2017-11-29 17:43                     ` Eric Abrahamsen
2017-12-12 12:26                   ` Michael Heerdegen
2017-12-12 17:17                     ` Eric Abrahamsen
2017-12-13 12:42                       ` Michael Heerdegen
2017-12-13 18:03                         ` Eric Abrahamsen
2017-12-14 11:31                           ` Michael Heerdegen
2017-12-14 23:41                             ` Eric Abrahamsen
2017-12-15 11:38                               ` Michael Heerdegen
2017-12-15 17:58                                 ` Eric Abrahamsen
2017-12-15 19:54                                   ` Michael Heerdegen
2017-12-16  6:10                                     ` Eric Abrahamsen
2017-12-28 20:30                                       ` Eric Abrahamsen
2017-12-14 15:30                           ` Michael Heerdegen
2017-12-14 16:05                             ` Michael Heerdegen
2017-12-14 16:59                               ` Eric Abrahamsen
2017-12-14 17:25                                 ` Michael Heerdegen
2017-12-14 17:54                                   ` Eric Abrahamsen
2017-12-16 12:21                       ` Michael Heerdegen
2017-12-16 21:08                         ` Eric Abrahamsen
2017-12-18 11:40                           ` Michael Heerdegen
2017-12-18 19:04                             ` Eric Abrahamsen
2017-12-19 14:27                               ` Michael Heerdegen
2017-12-19 16:14                                 ` Eric Abrahamsen
2017-11-28  7:44               ` Michael Heerdegen
2017-11-26  5:49           ` Michael Heerdegen
2017-10-15 15:43 ` Narendra Joshi

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=874lr3pz2q.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=help-gnu-emacs@gnu.org \
    /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).