all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Gnus: Thread notes?
Date: Sat, 25 Nov 2017 03:42:48 +0100	[thread overview]
Message-ID: <87fu93ulhz.fsf@web.de> (raw)
In-Reply-To: <878tgavoio.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Mon, 16 Oct 2017 13:14:23 -0700")

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> Anyway, please report bugs/feature requests. I've gotten a bit
> distracted from Gnorb while working on EBDB, and now attacking bits of
> Gnus, but it's really all the same project.

Can I ask some more usage questions?

I have a thread where I want to mark some Emails as "to do" and store
some notes about them (about what's important in them, and what I have
to do).  The thread already had become longish before I decided to use
Gnorb on it.

Did I do it right?  At first, I used `org-capture' (on the
chronologically first message that seemed relevant) to create a new org
headline for the thread.  I think this message didn't get a "&" in the
summary before I explicitly added another note for it with
`gnorb-gnus-incoming-do-todo' - is this expected?

Then I `gnorb-gnus-incoming-do-todo' on the other messages in this
thread that seemed important to add notes about them.  That worked, and
I also got the "&", though I wished these notes where explicitly linked
with the corresponding message ids in the org buffer - can I let Gnorb
do this automatically?  I can C-c v on the note, but that doesn't show
me which note corresponds to which message, and vice versa.

When I opened the group again, the relevant messages were not visible
(because they now were "old").  I had to / o in the summary buffer (btw,
is there a way to let A T fetch and show also "old" messages so that I
get the complete thread without / o?), I then marked the relevant
messages "important" ("!") so that they were shown the next time.

From the org buffer, I get the C-c v (`gnorb-org-view') thing working,
but every time I want to use, seems I have to go to the server buffer
(^) to make it work - when I don't do this I get user-error: "Please add
a "nngnorb" backend to your gnus installation".  Do you have a clue why
this happens and how I can solve it?

Finally, is there a way to show the complete thread from the Gnorb nnir
group buffer?

Please excuse my ignorance, I'm not really a Gnus expert...


Thanks,

Michael.



  parent reply	other threads:[~2017-11-25  2:42 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fu93ulhz.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.