Gnus development mailing list
 help / color / mirror / Atom feed
From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: Envelope sender lost from sending after gnus-draft-edit-message
Date: Mon, 24 Feb 2003 08:03:00 +0100	[thread overview]
Message-ID: <84k7fq17q3.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: <l6vwujqsnrz.fsf@williams.mc.vanderbilt.edu>

"Andrew A. Raines" <drew@poured.net> writes:

> What's the difference sendmail-wise between hitting `C-c C-c' on a
> newly composed messge and doing it after `D e'?

Gnus (sometimes) passes "-f foo" as an arg to sendmail, where the foo
comes from a (buffer-local?) variable.  If you store the message in
the drafts group, then edit it from there, the variable might have
another value altogether, especially if the original value was
buffer-local to begin with.

Maybe it would work to remember all buffer-local variables when
saving a draft, so that they can be restored on `D e'.

To fix this particular problem, only the value for the -f arg needs
to be remembered, though.

(From a later message I gather that you think that Gnus has a bug
there.  I agree.  I don't think that Jesper wanted to convince you
there is no bug, he just wanted to explain.)
-- 
A preposition is not a good thing to end a sentence with.



  parent reply	other threads:[~2003-02-24  7:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-11 17:03 Drew Raines
2003-02-22 21:00 ` Lars Magne Ingebrigtsen
2003-02-23 21:14   ` Andrew A. Raines
2003-02-23 21:35     ` Jesper Harder
2003-02-24  5:29       ` Andrew A. Raines
2003-03-01 22:11       ` Andrew A. Raines
2003-02-24  7:03     ` Kai Großjohann [this message]
2003-02-24 16:58       ` Andrew A. Raines
2003-02-24 19:09         ` Andrew A. Raines
2003-02-24 19:42         ` Kai Großjohann
2003-03-01 23:46 Jesper Harder
2003-03-02  0:25 ` Andrew A. Raines
2003-03-02  0:50   ` Jesper Harder
2003-03-02  6:24     ` Andrew A. Raines
2003-03-02 16:47       ` Jesper Harder

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