Gnus development mailing list
 help / color / mirror / Atom feed
From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: [patch] message-fetch-field, message-remove-header called
Date: Fri, 06 Jun 2003 23:07:00 +0200	[thread overview]
Message-ID: <84ptlq3ogb.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: <wc3he7dk2zc.fsf@gamma.cis.ohio-state.edu>

Benjamin Rutt <rutt+news@cis.ohio-state.edu> writes:

> I believe that `message-fetch-field' and `message-remove-header'
> should only be called when the message buffer has been narrowed to the
> headers.  I have found that this is not always the case in message.el.
> As a result, there are a few flaws in some callers of the above said
> functions, and I've attached a patch below.

Thank you very much.  I very slightly extended your docstring change
and committed this.

Gnah.  I wish I had fencepost access so I didn't have to ask for the
copyright situation every time.  Or maybe a less bad memory would be
sufficient.  This time, I'm too ashamed to ask...

I've tried various addresses to reactivate my fencepost account; does
anyone here know which one works?  (I believe system-hackers sent me
a nice autoreply, but nothing happened.)
-- 
This line is not blank.



  reply	other threads:[~2003-06-06 21:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-29 18:43 [patch] message-fetch-field, message-remove-header called improperly Benjamin Rutt
2003-06-06 21:07 ` Kai Großjohann [this message]
2003-06-06 23:40   ` [patch] message-fetch-field, message-remove-header called Simon Josefsson
2003-06-07  1:03   ` Benjamin Rutt

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=84ptlq3ogb.fsf@lucy.is.informatik.uni-duisburg.de \
    --to=kai.grossjohann@gmx.net \
    /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).