From: Mark Plaksin <happy@usg.edu>
Subject: Re: verbatim text (mm-uu.el): blank lines
Date: Sat, 08 Oct 2005 08:29:58 -0400 [thread overview]
Message-ID: <87hdbs42ex.fsf@stone.tss.usg.edu> (raw)
In-Reply-To: <v9hdbs2rn3.fsf@marauder.physik.uni-ulm.de>
[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]
Reiner Steib <reinersteib+gmane@imap.cc> writes:
> On Sat, Oct 08 2005, Adam Duck wrote:
>
>> Hmm, [...] I see the blank lines.
>
> Thanks. I found that my settings are causing this:
>
> (setq
> gnus-treat-strip-leading-blank-lines t
> gnus-treat-strip-trailing-blank-lines t)
Fascinating! I have had a similar issue involving
gnus-treat-strip-trailing-blank-lines. I haven't gotten to the bottom of
it yet.
If I have this:
(setq
gnus-treat-hide-signature t
gnus-treat-strip-leading-blank-lines t
gnus-treat-strip-multiple-blank-lines t
gnus-treat-strip-trailing-blank-lines t)
then I can't unhide the signatures of certain messages--most notably mail
from majordomo. If I set gnus-treat-strip-trailing-blank-lines to nil,
then everything works as expected. The problem only occurs when
gnus-treat-strip-trailing-blank-lines is t before I read the article. I
can't reproduce the problem by running
gnus-article-remove-trailing-blank-lines from the Summary buffer. A sample
majordomo message is attached.
> I'll try, if the following is okay for me (usually I don't want to see
> the leading/trailing blank lines):
>
> (setq
> gnus-treat-strip-leading-blank-lines 'last
> gnus-treat-strip-trailing-blank-lines gnus-treat-strip-leading-blank-lines)
This doesn't help my situation.
[-- Attachment #2: msg --]
[-- Type: text/plain, Size: 885 bytes --]
Return-Path: <Majordomo-Owner@psg.com>
Received: from psg.com (psg.com [147.28.0.62])
by hermes.bor.usg.edu (8.12.11/8.12.11) with ESMTP id j3S2QGq7029979
for <happy@usg.edu>; Wed, 27 Apr 2005 22:26:16 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
id 1DQyjH-000KRG-Sm
for happy@usg.edu; Thu, 28 Apr 2005 02:26:15 +0000
To: happy@usg.edu
From: majordomo@psg.com
Subject: Majordomo results: Re: Confirmation for unsubscribe namedro
Reply-To: majordomo@psg.com
Message-Id: <E1DQyjH-000KRG-Sm@psg.com>
Date: Thu, 28 Apr 2005 02:26:15 +0000
X-USG-MailScanner: Found to be clean
X-USG-MailScanner-SpamCheck: not spam, SpamAssassin (score=-2.538,
required 5, AWL 0.05, BAYES_00 -2.60, NO_REAL_NAME 0.01)
X-MailScanner-From: majordomo-owner@psg.com
--
>>>> auth 80a3acb58fd8f1641bb263048290d25d unsubscribe namedroppers happy@usg.edu
Succeeded.
>>>>
next prev parent reply other threads:[~2005-10-08 12:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 19:42 Reiner Steib
2005-10-07 22:50 ` Adam Duck
2005-10-08 11:08 ` Reiner Steib
2005-10-08 12:29 ` Mark Plaksin [this message]
2005-10-10 16:49 ` Reiner Steib
2005-10-12 1:19 ` Katsumi Yamaoka
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=87hdbs42ex.fsf@stone.tss.usg.edu \
--to=happy@usg.edu \
/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).