From: Michael Cook <mcook@cognex.com>
Subject: [sgnus 0.13] bug: mail-position-on-field
Date: Sat, 18 Nov 1995 15:09:17 -0500 [thread overview]
Message-ID: <199511182009.PAA17497@erawan.cognex.com> (raw)
In `gnus-msg.el', the fun `gnus-inews-insert-bfcc' invokes
`gnus-inews-narrow-to-headers' and then tries to invoke
`mail-position-on-field' which searches for the `--text follows this line--'
marker that follows the headers. Because the buffer has been narrowed, the
search fails and an error signal is thrown.
I modified `gnus-inews-insert-bfcc' like this:
(defun gnus-inews-insert-bfcc ()
"Insert Bcc and Fcc headers."
(save-excursion
(save-restriction
;(gnus-inews-narrow-to-headers) ;<---- commented out this line
and the problem went away.
Michael.
reply other threads:[~1995-11-18 20:09 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=199511182009.PAA17497@erawan.cognex.com \
--to=mcook@cognex.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).