From: Kai Grossjohann <grossjoh@dusty.informatik.uni-dortmund.de>
Subject: 0.28 and gnus-article-hide-boring-headers
Date: Wed, 17 Jan 96 09:59:09 +0100 [thread overview]
Message-ID: <9601170859.AA24652@dusty.informatik.uni-dortmund.de> (raw)
Hi all,
in gnus.el, at line 13133 in function
gnus-article-hide-boring-headers, I changed the code to read thusly:
((eq elem 'reply-to)
;;- Kai added stringp tests here
(when (and (stringp (mail-fetch-field "from"))
(stringp (mail-fetch-field "reply-to"))
(equal (nth 1 (mail-extract-address-components
(mail-fetch-field "from")))
(nth 1 (mail-extract-address-components
(mail-fetch-field "reply-to")))))
(gnus-article-hide-header "reply-to")))
I added the two stringp tests. Was this the right thing to do? What
should I have done instead?
The symptom was that mail-extract-address-components got called with a
nil argument which it didn't like at all.
kai
--
I like both kinds of music.
next reply other threads:[~1996-01-17 8:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-01-17 8:59 Kai Grossjohann [this message]
1996-01-17 8:59 Kai Grossjohann
1996-01-17 12:27 ` Kai Grossjohann
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=9601170859.AA24652@dusty.informatik.uni-dortmund.de \
--to=grossjoh@dusty.informatik.uni-dortmund.de \
--cc=grossjoh@charly.informatik.uni-dortmund.de \
/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).