From: Robert Bihlmeyer <e9426626@stud4.tuwien.ac.at>
Subject: Re: Making message/rfc822 boundaries visible
Date: 12 Oct 1999 12:50:23 +0200 [thread overview]
Message-ID: <lfiu4c26q8.fsf@mars.zserv.tuwien.ac.at> (raw)
In-Reply-To: Jack Vinson's message of "11 Oct 1999 11:13:34 -0500"
Hi,
>>>>> On 11 Oct 1999 11:13:34 -0500
>>>>> Jack Vinson <vinson@unagi.cis.upenn.edu> said:
Jack> What is wrong with setting gnus-inhibit-mime-unbuttonizing to
Jack> 't? This gives me buttons before each part of a mime message.
I don't want buttons all over the place. Francois has convinced me
that they are normally not necessary. I don't need a button to see
where an inlined image start, I can see it by myself. I can also
usually infer where inlined C/elisp/patches start and end, if I want
to know this at all.
Inlined message/rfc822 parts are of a different kind. The beginning is
visible in some configurations, the end too, in some cases. But I want
some indications where the boundaries are, that work everytime. Seeing
the structure of a double-bounce that has been forwarded to you is not
easy without some help. Buttons are one possibility, my code is
another.
Robbe
--
Robert Bihlmeyer reads: Deutsch, English, MIME, Latin-1, NO SPAM!
<robbe@orcus.priv.at> <http://stud2.tuwien.ac.at/~e9426626/sig.html>
prev parent reply other threads:[~1999-10-12 10:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-10 21:57 Robert Bihlmeyer
1999-10-11 16:13 ` Jack Vinson
1999-10-10 19:40 ` François Pinard
1999-10-11 21:29 ` Kai Großjohann
1999-10-11 22:11 ` Jack Vinson
1999-10-12 9:53 ` Toby Speight
1999-11-06 21:48 ` Lars Magne Ingebrigtsen
1999-10-12 16:36 ` Florian Weimer
1999-10-11 18:58 ` François Pinard
1999-10-13 5:56 ` Florian Weimer
1999-10-13 9:46 ` Toby Speight
1999-10-13 14:37 ` François Pinard
1999-11-06 21:47 ` Lars Magne Ingebrigtsen
1999-10-12 10:50 ` Robert Bihlmeyer [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=lfiu4c26q8.fsf@mars.zserv.tuwien.ac.at \
--to=e9426626@stud4.tuwien.ac.at \
/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).