From: kbk@shore.net (Kurt B. Kaiser)
Subject: Re: Digest with Headers
Date: Tue, 12 Nov 2002 21:23:18 GMT [thread overview]
Message-ID: <m3of8uscs8.fsf@float.attbi.com> (raw)
In-Reply-To: <v9u1ipehow.fsf@marauder.physik.uni-ulm.de>
Reiner Steib <4uce.02.r.steib@gmx.net> writes:
> On Sat, Nov 09 2002, Kai Großjohann wrote:
>
> > kbk@shore.net (Kurt B. Kaiser) writes:
> >
> >> S o m will forward an email with its headers, but I can't figure out
> >> how to send a digest wherein each article is sent with its full headers.
> [...]
> > See the variable gnus-uu-digest-headers. It's kind of a backward way
> > to achieve it, but better backward than none.
>
> If you need it more often, you may want to define a function (and bind
> it to some key):
>
> (defun rs-gnus-uu-digest-mail-forward-all-headers (&optional n post)
> (interactive)
> (let* ((gnus-uu-digest-headers nil))
> (gnus-uu-digest-mail-forward n post)))
>
> I think the doc-string should mention that nil means all headers. I
> thought that '("^.*:") would do it, but it didn't.
>
> ,----[ C-h v gnus-uu-digest-headers RET ]
> | gnus-uu-digest-headers's value is
> | ("^Date:" "^From:" "^To:" [...] "^Content-ID:")
> |
> | Documentation:
> | *List of regexps to match headers included in digested messages.
> | The headers will be included in the sequence they are matched.
> `----
Thanks to all of you for your help on this. Works great!
Regards, KBK
prev parent reply other threads:[~2002-11-12 21:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3fzubvktn.fsf@float.attbi.com>
2002-11-09 20:45 ` Jesper Harder
[not found] ` <m3fzua2hb1.fsf@float.attbi.com>
2002-11-10 12:06 ` Jesper Harder
2002-11-10 13:01 ` Vasily Korytov
[not found] ` <84of8ykaz0.fsf@crybaby.uni-duisburg.de>
[not found] ` <v9u1ipehow.fsf@marauder.physik.uni-ulm.de>
2002-11-12 21:23 ` Kurt B. Kaiser [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=m3of8uscs8.fsf@float.attbi.com \
--to=kbk@shore.net \
/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).