From: Rodolfo Medina <rodolfo.medina@gmail.com>
To: info-gnus-english@gnu.org
Subject: Re: Hidden lines in the message body
Date: Mon, 10 Sep 2007 13:59:40 +0200 [thread overview]
Message-ID: <878x7eafyr.fsf@gmail.com> (raw)
In-Reply-To: <b4mfy1n2vhv.fsf@jpl.org>
Rodolfo Medina wrote:
>> I' attaching a text file containing eight lines. If I insert it in a message
>> (e.g. with `C-x i') and then send the message, in the message body only the
>> first and the fifth will be visible, the others won't.
>
>> Can anybody explain why this happens and how to avoid it?
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> It is because of the MIME emulating feature of Gnus that is
> enabled by default. It splits peculiar sections, e.g. uuencoded
> data, non-MIME forwarded messages, etc., in the message body into
> MIME parts. Your problem is a typical case that this feature
> works unwillingly, that is, Gnus misidentifies the
> "------------------------------%<------------------------------"
> lines as the separators of the `insert-marks' part (See mm-uu.el).
>
> The MIME emulating feature works only when displaying articles.
> So, your messages will never be broken even if they look funny
> to the recipients who use Gnus. But there is no way to avoid it
> other than to ask the recipients to disable this feature. To do
> that:
>
> --8<---------------cut here---------------start------------->8---
> (setq gnus-article-emulate-mime nil)
> --8<---------------cut here---------------end--------------->8---
>
> or
>
> --8<---------------cut here---------------start------------->8---
> (eval-after-load "mm-uu"
> '(add-to-list 'mm-uu-configure-list
> '(insert-marks . disabled)))
> --8<---------------cut here---------------end--------------->8---
Thanks.
The problem seems to be solved since I put in .gnus.el the line:
(setq gnus-article-emulate-mime nil)
1) Is that what you meant? (I don't well understand the meaning of the lines
where it says `cut here', `start', `end'.)
2) Won't there be any unwished side effects with other messages (e.g.,
including attachments)?
Thanks indeed, cheers
Rodolfo
next prev parent reply other threads:[~2007-09-10 11:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-08 20:54 Rodolfo Medina
2007-09-10 0:51 ` Katsumi Yamaoka
2007-09-10 11:59 ` Rodolfo Medina [this message]
2007-09-10 17:10 ` Daniel C. Bastos
2007-09-11 1:01 ` 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=878x7eafyr.fsf@gmail.com \
--to=rodolfo.medina@gmail.com \
--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).