From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: why article refresh in gnus-summary-edit-article?
Date: 25 Sep 1999 12:12:09 +0200 [thread overview]
Message-ID: <m3u2oj2tc6.fsf@quimbies.gnus.org> (raw)
In-Reply-To: "Rupa Schomaker's message of "24 Sep 1999 12:20:33 -0700"
"Rupa Schomaker (list)" <rupa-list@rupa.com> writes:
> 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...
I don't know whether that would be generally useful. I think it might
be better for you to alter the functions to do what you want them to
do...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1999-09-25 10:12 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)
1999-09-25 10:12 ` Lars Magne Ingebrigtsen [this message]
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=m3u2oj2tc6.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
/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).