Gnus development mailing list
 help / color / mirror / Atom feed
From: Robert Bihlmeyer <robbe@orcus.priv.at>
Subject: Making message/rfc822 boundaries visible
Date: 10 Oct 1999 23:57:28 +0200	[thread overview]
Message-ID: <wsu2nyhoaf.fsf@orcus.priv.at> (raw)

[-- Attachment #1: Type: text/plain, Size: 323 bytes --]

Hi,

I finally decided to stop whining, and provide some code. The
following, when put into your .gnus file, will render brackets around
message/rfc822 parts, so you can see where an inlined message begins
and ends. Nesting works out nice, too. Tested under XEmacs 21.1, but
IIRC markers are also provided by FSF Emacsen.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-emacs-lisp, Size: 386 bytes --]

(setf (cadr (assoc "message/rfc822" mm-inline-media-tests))
      'mm-inline-message-bracketed)

(defun mm-inline-message-bracketed (handle)
  (insert ",---\n")
  (let ((end (point-marker)))
    (set-marker-insertion-type end t)
    (mm-inline-message handle)
    (while (< (point) end)
      (insert "| ")
      (beginning-of-line 2))
    (move-marker end nil)
    (insert "`---\n")))

[-- Attachment #3: Type: text/plain, Size: 237 bytes --]


Adapting this to other types which have nonobviouse boundaries is
easy.

        Robbe

-- 
Robert Bihlmeyer       reads: Deutsch, English, MIME, Latin-1, NO SPAM!
<robbe@orcus.priv.at>    <http://stud2.tuwien.ac.at/~e9426626/sig.html>

             reply	other threads:[~1999-10-10 21:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-10 21:57 Robert Bihlmeyer [this message]
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

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=wsu2nyhoaf.fsf@orcus.priv.at \
    --to=robbe@orcus.priv.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).