From: morioka@jaist.ac.jp (守岡 知彦 / MORIOKA Tomohiko)
Subject: Re: Display glitches in sgnus 0.83 (II)
Date: 20 May 1996 02:37:52 +0900 [thread overview]
Message-ID: <s1cbujkva1b.fsf@jaist.ac.jp> (raw)
In-Reply-To: morioka@jaist.ac.jp's message of 20 May 1996 02:17:58 +0900
[-- Attachment #1.1: Type: text/plain, Size: 1738 bytes --]
>>>>> In <s1cu3xc8tvc.fsf@jaist.ac.jp>
>>>>> morioka@jaist.ac.jp (MORIOKA Tomohiko) wrote:
tomo> >>>>> In <x6zq74ejfa.fsf@eyesore.no>
tomo> >>>>> Lars Magne Ingebrigtsen <larsi@ifi.uio.no> wrote:
Lars> Steven L Baur <steve@miranova.com> writes:
Steven>> Enabling gnus-article-hide-signature in the
Steven>> gnus-article-display-hook is still too aggressive. It should
Steven>> not cross MIME multipart boundaries.
Lars> To deal with that properly, Gnus would have to do some MIME
Lars> parsing, which is something I'd rather not get into. An easy
Lars> hack would be to set `gnus-signature-limit' to "^--Multipart" or
Lars> something -- that way signatures that contain that regexp
Lars> wouldn't be hidden. Is that nice, though?
tomo> Following code is available for tm-view MIME processing. It may be
tomo> safe even if tm-view is not used:
(snip)
Following code is available to MIME safe signature handling using
tm-view:
(defun gnus-narrow-to-signature ()
"Narrow to the signature."
(widen)
(if (and (boundp 'mime::preview/content-list)
mime::preview/content-list)
(let ((pcinfo (car (last mime::preview/content-list))))
(narrow-to-region (mime::preview-content-info/point-min pcinfo)
(point-max))
))
(goto-char (point-max))
(when (re-search-backward gnus-signature-separator nil t)
(forward-line 1)
(when (or (null gnus-signature-limit)
(and (numberp gnus-signature-limit)
(< (- (point-max) (point)) gnus-signature-limit))
(and (gnus-functionp gnus-signature-limit)
(funcall gnus-signature-limit))
(and (stringp gnus-signature-limit)
(not (re-search-forward gnus-signature-limit nil t))))
(narrow-to-region (point) (point-max))
t)))
[-- Attachment #1.2: Type: text/plain, Size: 324 bytes --]
----------------------------------------------------------------------
MORIOKA Tomohiko <morioka@jaist.ac.jp>
Japan advanced Institute of Science and Technology, Hokuriku
Asahi-dai, Tatsu-no-kuchi chô, Nomi, Ishikawa, Japan
----------------------------------------- Frisch, Frei, Freöhlich! ---
[-- Attachment #2: Type: application/pgp-signature, Size: 345 bytes --]
prev parent reply other threads:[~1996-05-19 17:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-09 17:56 Steven L Baur
1996-05-19 16:07 ` Lars Magne Ingebrigtsen
1996-05-19 17:04 ` Per Abrahamsen
1996-05-19 18:21 ` Lars Magne Ingebrigtsen
1996-05-20 8:52 ` Kai Grossjohann
1996-05-20 20:54 ` [++] " Colin Rafferty
1996-05-20 22:21 ` Lars Magne Ingebrigtsen
1996-05-19 17:17 ` 守岡 知彦 / MORIOKA Tomohiko
1996-05-19 17:37 ` 守岡 知彦 / MORIOKA Tomohiko [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=s1cbujkva1b.fsf@jaist.ac.jp \
--to=morioka@jaist.ac.jp \
/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).