Gnus development mailing list
 help / color / mirror / Atom feed
From: Jesper Harder <harder@ifa.au.dk>
Subject: Re: Buttonizing and decoding based on message part contents?
Date: Wed, 17 Dec 2003 00:08:22 +0100	[thread overview]
Message-ID: <m3zndsxswp.fsf@defun.localdomain> (raw)
In-Reply-To: <m3k74w395r.fsf@asfast.com> (Lloyd Zusman's message of "Tue, 16 Dec 2003 13:33:04 -0500")

Lloyd Zusman <ljz@asfast.com> writes:

> What I want to do is to look into each part and see if it contains a
> block of text between the markers "-----BEGIN PGP MESSAGE-----" and
> "-----END PGP MESSAGE-----", and if so, to either buttonize it or force
> it to be decoded via pgg (or both).
>
> Is there some sort of hook mechanism that will allow me to install an
> optional function to test each message part and as a result of this
> test, to set its buttonizing or decoding attributes?

No. `mm-uu-dissect' which is the function responsible for detecting
this is only applied to single part text/plain.

I think this feature has been requested several times (and ISTR
previous discussions here).  Look around line 4495 in gnus-art.el if
you'd like to experiment with it.

> Or perhaps is there another way to do this?

Another possibility could be to do it as a part of article washing --
something like the removed `article-hide-pgp' from Gnus 5.9.



  reply	other threads:[~2003-12-16 23:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-16 18:33 Lloyd Zusman
2003-12-16 23:08 ` Jesper Harder [this message]
2003-12-17 13:19   ` Lloyd Zusman
2003-12-17 13:49     ` Jesper Harder
2003-12-17 14:04       ` Lloyd Zusman
2003-12-17 15:13         ` Jesper Harder
2003-12-17 15:43           ` Lloyd Zusman
2003-12-17 22:13             ` Jesper Harder
2003-12-18 17:30               ` Lloyd Zusman
2003-12-19  1:17                 ` Jesper Harder
2003-12-19 18:26                   ` Lloyd Zusman

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=m3zndsxswp.fsf@defun.localdomain \
    --to=harder@ifa.au.dk \
    /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).