From: Jack Vinson <vinson@unagi.cis.upenn.edu>
Subject: Re: Making message/rfc822 boundaries visible
Date: 11 Oct 1999 11:13:34 -0500 [thread overview]
Message-ID: <wk1zb1ub81.fsf@chevax.ecs.umass.edu> (raw)
In-Reply-To: Robert Bihlmeyer's message of "10 Oct 1999 23:57:28 +0200"
>>>>> "Robbe" == Robert Bihlmeyer <robbe@orcus.priv.at> writes:
Robbe> I finally decided to stop whining, and provide some code. The
Robbe> following, when put into your .gnus file, will render brackets around
Robbe> message/rfc822 parts, so you can see where an inlined message begins
Robbe> and ends. Nesting works out nice, too. Tested under XEmacs 21.1, but
Robbe> IIRC markers are also provided by FSF Emacsen.
What is wrong with setting gnus-inhibit-mime-unbuttonizing to 't? This
gives me buttons before each part of a mime message. Ellipses (...) after
a button indicates that it has not been "expanded," either because it is
not inlinable or because my setup keeps it from inlining automatically.
--
Jack Vinson
Bart: I will not charge admission to the bathroom.
next prev parent reply other threads:[~1999-10-11 16:13 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 [this message]
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
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=wk1zb1ub81.fsf@chevax.ecs.umass.edu \
--to=vinson@unagi.cis.upenn.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).