From: "Rupa Schomaker (list)" <rupa-list@rupa.com>
Subject: Re: why article refresh in gnus-summary-edit-article?
Date: 24 Sep 1999 12:20:33 -0700 [thread overview]
Message-ID: <m3puz8glq6.fsf@gw.rupa.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "24 Sep 1999 18:16:47 +0200"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> "Rupa Schomaker (list)" <rupa-list@rupa.com> writes:
>
> > I'm not sure what would break if we didn't reload the article before
> > calling the -edit base. Anyone know?
>
> Well, you would face having to edit something that has been washed
> pretty severly. For instance, many of the headers would be gone, and
> so on.
Ah, very good point! <ponder> The last thing I really want to happen
is for the decrypted message to actually be saved to the message store
(currently I think this does happen for backends that support
editing). Would it be reasonable to add an optional argument to -edit
that tells it not to do a reload of the article. Then something that
wants to do the -edit and *knows* that it shouldn't do an article
reload could communicate that fact to -edit...
--
Rupa (rupa@rupa.com for normal email)
Please don't email duplicate replies.
next prev parent reply other threads:[~1999-09-24 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-17 1:50 Rupa Schomaker (list)
1999-09-24 16:16 ` Lars Magne Ingebrigtsen
1999-09-24 19:20 ` Rupa Schomaker (list) [this message]
1999-09-25 10:12 ` Lars Magne Ingebrigtsen
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=m3puz8glq6.fsf@gw.rupa.com \
--to=rupa-list@rupa.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).