From: Lloyd Zusman <ljz@asfast.com>
Subject: Re: Completely removing an article from drafts?
Date: Mon, 12 May 2003 08:57:46 -0400 [thread overview]
Message-ID: <7k8w4911.fsf@asfast.com> (raw)
In-Reply-To: <vxkd6ioicau.fsf@mesquite.charcoal.com> (Karl Kleinpaste's message of "Mon, 12 May 2003 08:23:21 -0400")
Karl Kleinpaste <k@charcoal.com> writes:
> Lloyd Zusman <ljz@asfast.com> writes:
>> Since `gnus-summary-delete-article' does actual expiry, I think
>> that it would be more clear if "expire" appeared in the function name.
>
> No, I don't agree. "Expiry" in Gnus is generally a time-based
> concept; an article expires after a timeout passes, causing deletion.
>
> gnus-summary-delete-article simply deletes, right now. It does not
> expire anything; it annihilates something on the spot. For "delete,"
> dictionary.reference.com says "To remove by striking out or
> canceling", and that's what the function does.
>
> I think it is named exactly right.
In addition to what I wrote in my previous message, I want to add that
`gnus-summary-delete-article' does _not_ delete an article using the
dictionary definition of "delete" that you mention above. Check the
documentation and the source code. What that function actually does is
to _expire_ the article, in the exact manner that Gnus defines _expire_.
What `gnus-summary-delete-article' actually does is to apply
`nnimap-expiry-function' to the article. If `nnimap-expiry-function' is
set to 'delete, then `gnus-summary-delete-article' will indeed do a
deletion as the expiry process that it performs. However, if that
variable contains a function symbol, that function is invoked to perform
the expiry.
Therefore, `gnus-summary-delete-article' is indeed a misnomer for this
function, and `gnus-summary-expire-article' is the perfectly precise
name for what this function actually does.
--
Lloyd Zusman
ljz@asfast.com
next prev parent reply other threads:[~2003-05-12 12:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 9:32 Lloyd Zusman
2003-05-12 10:27 ` Jochen Küpper
2003-05-12 10:59 ` Lloyd Zusman
2003-05-12 11:20 ` Karl Kleinpaste
2003-05-12 12:03 ` Lloyd Zusman
2003-05-12 12:23 ` Karl Kleinpaste
2003-05-12 12:47 ` Lloyd Zusman
2003-05-12 12:59 ` Karl Kleinpaste
2003-05-12 13:11 ` Lloyd Zusman
2003-05-12 13:37 ` Karl Kleinpaste
2003-05-12 14:29 ` Lloyd Zusman
2003-05-12 13:18 ` Lloyd Zusman
2003-05-14 19:55 ` Kai Großjohann
2003-10-18 13:48 ` Lars Magne Ingebrigtsen
2003-05-14 19:53 ` Kai Großjohann
2003-05-12 12:57 ` Lloyd Zusman [this message]
2003-05-12 16:27 ` Lloyd Zusman
2003-05-12 11:57 ` Simon Josefsson
2003-05-12 12:12 ` Lloyd Zusman
2003-05-12 13:45 ` Jochen Küpper
2003-05-12 18:32 ` David S Goldberg
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=7k8w4911.fsf@asfast.com \
--to=ljz@asfast.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).