Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Karl Kleinpaste <karl@charcoal.com>
Subject: Re: expanding a digest
Date: Sun, 18 Sep 2005 00:32:49 -0400	[thread overview]
Message-ID: <vxky85vuham.fsf@mesquite.charcoal.com> (raw)
In-Reply-To: <mailman.7380.1127014071.20277.info-gnus-english@gnu.org>

Allan Gottlieb <gottlieb@nyu.edu> writes:
> I prefer to receive some mailing lists in digest form.
> What command should I execute so that the selected digest (or all
> ticked digests) are expanded and appear in the summary buffer as if
> they were the individual messages?

C-d runs `gnus-summary-enter-digest-group'

`gnus-summary-enter-digest-group' is an interactive compiled Lisp function
  -- loaded from "gnus-sum"
(gnus-summary-enter-digest-group &optional FORCE)

Documentation:
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.


      reply	other threads:[~2005-09-18  4:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-18  3:25 Allan Gottlieb
2005-09-18  4:32 ` Karl Kleinpaste [this message]

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=vxky85vuham.fsf@mesquite.charcoal.com \
    --to=karl@charcoal.com \
    --cc=karl+usenet@charcoal.com \
    /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).