From: Emanuel Berg <embe8573@student.uu.se>
To: info-gnus-english@gnu.org
Subject: Re: Loss of first paragraph on fill and reply
Date: Tue, 12 Nov 2013 04:21:50 +0100 [thread overview]
Message-ID: <874n7i2tjs.fsf@nl106-137-194.student.uu.se> (raw)
In-Reply-To: <87ob5q2v9w.fsf@nl106-137-194.student.uu.se>
Emanuel Berg <embe8573@student.uu.se> writes:
> Wow - for all my stupidity in this thread, I have to
> say my intuition is amazing! Yes, it was the
> headers. Specifically, this line:
>
> ;; don't show any headers
> (setq gnus-visible-headers "^XXX")
>
> So the, ehm, *followup* question is: what is the
> correct way to hide all headers, naturally without
> breaking the fill and "followup with original"
> functions? (And possibly other functions as well.)
This attempt has the same problem:
;; (setq gnus-visible-headers nil)
;; (setq gnus-ignored-headers '("^.*:"))
--
Emanuel Berg, programmer-for-rent. CV, projects, etc at uXu
underground experts united: http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2013-11-12 3:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-10 14:14 Emanuel Berg
2013-11-10 18:23 ` Dmitrii Kashin
[not found] ` <mailman.5731.1384107817.10748.info-gnus-english@gnu.org>
2013-11-10 21:14 ` Emanuel Berg
2013-11-10 22:34 ` Dmitrii Kashin
[not found] ` <mailman.5771.1384122902.10748.info-gnus-english@gnu.org>
2013-11-12 0:54 ` Emanuel Berg
2013-11-12 1:58 ` Dmitrii Kashin
[not found] ` <mailman.5851.1384221526.10748.info-gnus-english@gnu.org>
2013-11-12 2:44 ` Emanuel Berg
2013-11-12 3:21 ` Emanuel Berg [this message]
2013-11-12 6:57 ` Dmitrii Kashin
[not found] ` <mailman.5865.1384239506.10748.info-gnus-english@gnu.org>
2013-11-12 21:09 ` Emanuel Berg
2013-11-13 7:08 ` Dmitrii Kashin
[not found] ` <mailman.5948.1384326540.10748.info-gnus-english@gnu.org>
2013-11-13 19:47 ` Emanuel Berg
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=874n7i2tjs.fsf@nl106-137-194.student.uu.se \
--to=embe8573@student.uu.se \
--cc=info-gnus-english@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 NNTP newsgroup(s).