From: Karl Kleinpaste <karl@jprc.com>
Subject: buglet in p0.40 nnheader.el xref handling [patch]
Date: 26 Oct 1998 23:16:35 -500 [thread overview]
Message-ID: <vxkyaq2abbw.fsf@pocari-sweat.jprc.com> (raw)
I have some very, very old mail archives, predating ding entirely but
nnml-equivalent from the outset nonetheless, having no Xref: headers.
I have now set gnus-extra-headers and nnmail-extra-headers, which
leads to a desire to write Xref: fields, which fails when there is no
Xref content.
An invocation of nnml-generate-nov-databases tripped over this error.
OTOH, this creates an xref field with no content, which might not be
proper; I wasn't really sure, but it's not hurting me, as far as I can
see.
(Line numbers may vary, as I'm busy elsehow.)
--- nnheader.el.~1~ Sun Oct 25 21:56:09 1998
+++ nnheader.el Mon Oct 26 22:58:56 1998
@@ -350,7 +350,7 @@
(insert "\t")
(when (or (mail-header-xref header)
(mail-header-extra header))
- (insert "Xref: " (mail-header-xref header) "\t"))
+ (insert "Xref: " (or (mail-header-xref header) "") "\t"))
(when (mail-header-extra header)
(let ((extra (mail-header-extra header)))
(while extra
reply other threads:[~1998-10-27 4:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=vxkyaq2abbw.fsf@pocari-sweat.jprc.com \
--to=karl@jprc.com \
/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).