From: "Sebastian P. Luque" <spluque@gmail.com>
To: ding@gnus.org
Subject: Re: making separate messages from a single one
Date: Mon, 07 Jan 2008 14:10:31 -0600 [thread overview]
Message-ID: <87d4sdl7m0.fsf@patagonia.sebmags.homelinux.org> (raw)
In-Reply-To: <87k5mla0x8.fsf@obelix.mork.no>
On Mon, 07 Jan 2008 20:30:27 +0100,
Bjørn Mork <bmork@dod.no> wrote:
[...]
> C-d runs the command gnus-summary-enter-digest-group which is an
> interactive compiled Lisp function in `gnus-sum.el'. It is bound to
> C-d, A D, <menu-bar> <Article> <Enter digest buffer>.
> (gnus-summary-enter-digest-group &optional force)
> Enter an nndoc group based on the current article. If force, force a
> digest interpretation. If not, try to guess what the document format
> is.
Yes, thank you. However, although it results in the correct separate
messages, they are all from the same original author. In other words,
the correct message ends up buried in a message from the original author
who sent me the digest. I probably need a second step after that.
--
Seb
next prev parent reply other threads:[~2008-01-07 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 17:26 Sebastian P. Luque
2008-01-07 19:30 ` Bjørn Mork
2008-01-07 20:10 ` Sebastian P. Luque [this message]
2008-01-07 20:37 ` Reiner Steib
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=87d4sdl7m0.fsf@patagonia.sebmags.homelinux.org \
--to=spluque@gmail.com \
--cc=ding@gnus.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 NNTP newsgroup(s).