From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: Ding List <ding@gnus.org>
Subject: Re: Display of message/rfc822 parts in Loom
Date: Tue, 10 May 2005 19:05:08 +0200 [thread overview]
Message-ID: <v964xrf1vf.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <4280B9F8.6B64@xyzzy.claranet.de> (Frank Ellermann's message of "Tue, 10 May 2005 15:41:12 +0200")
[-- Attachment #1: Type: text/plain, Size: 857 bytes --]
On Tue, May 10 2005, Frank Ellermann wrote:
> Reiner Steib wrote:
>
>> the display of message/rfc822 parts in Loom is broken
>
> Another odddity: <strike>start</strike> (dito for end).
I'd vote for disabling the strikethru decoration feature. It produces
by far more false positives than intended decorations.
> <http://article.gmane.org/gmane.emacs.devel/36938/raw>
>
> The original article has a third text/plain inline part
> with a MIME-version: 1.0 header field. So far I thought
> that a part has zero or more Content- header fields,
> but not its very own MIME-version. Most probably it's
> perfectly legal, I've just not seen it anywhere before.
The "MIME-Version" header was inserted by Gnus on sending (not present
in the message buffer). I don't know if it should be there. -->
Cc-ing ding. `message-forward-as-mime' is t.
,----[
|
[-- Attachment #2: Type: message/rfc822, Size: 297 bytes --]
| From: "oliver" <oliver_baumann@nospam.justemail.net>
| Newsgroups: comp.emacs
| Subject: Preventing drag & drop the dired way
| Date: Tue, 10 May 2005 17:26:49 +1000
| Organization: Internet Customer
| Message-ID: <d5pngo$2oai$1@otis.netspace.net.au>
|
| Hi there,
| [...]
| MIME-Version: 1.0
[-- Attachment #3: Type: text/plain, Size: 261 bytes --]
`----
>> <news:v9y8anju0f.fsf@marauder.physik.uni-ulm.de>
>
> Harry Potter fan ? <g>
No, this hostname is older than the Harry Potter boom. ;-)
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
parent reply other threads:[~2005-05-10 17:05 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4280B9F8.6B64@xyzzy.claranet.de>]
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=v964xrf1vf.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=ding@gnus.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).