Gnus development mailing list
 help / color / mirror / Atom feed
From: Steve Youngs <youngs@xemacs.org>
Subject: Re: [PATCH] Make gnus-summary-delete-article respect group parameters
Date: Thu, 11 Jul 2002 21:36:42 +1000	[thread overview]
Message-ID: <microsoft-free.x465zmts1h.fsf@eicq.dnsalias.org> (raw)
In-Reply-To: <iluk7o5avk5.fsf@latte.josefsson.org> (Simon Josefsson's message of "Tue, 09 Jul 2002 15:18:50 +0200")

|--==> "SJ" == Simon Josefsson <jas@extundo.com> writes:

  SJ> Yup.  I also like B DEL to really delete the article, but I don't
  SJ> think it is important enough to modify existing behaviour.  Let's wait
  SJ> for someone to report it as a bug, and then we can discuss it. :-)

Well, consider this a bug report.  IMO, B DEL should ignore all group
parameters especially expiry settings.  The only thing that B DEL
should do is physically delete the article, completely, forever, do
not pass go, do not collect 200 euro, the judges decision is final, no
correspondence will be entered into.

And up until I read this thread I'd been merrily B DEL'ing all the
crud out of my mail groups.  Now I find out that they haven't been
deleted and are all hiding in my archives... sheesh.

Please, Gnus boys 'n' girls, make B DEL do what B DEL should... Bloody
DELete.

Besides, just look at the doc for it...

,----[ C-h k B DEL ]
| B DEL runs `gnus-summary-delete-article'
| 
| `gnus-summary-delete-article' is an interactive compiled Lisp function
|   -- loaded from "gnus-sum"
| (gnus-summary-delete-article &optional N)
| 
| Documentation:
| Delete the N next (mail) articles.
| This command actually deletes articles.	 This is not a marking
| command.  The article will disappear forever from your life, never to
| return.
| If N is negative, delete backwards.
| If N is nil and articles have been marked with the process mark,
| delete these instead.
`----

Now, I've read that a dozen or so times and I just can't make it mean
"when we say 'delete' we don't actually mean delete, we mean run the
article through the normal expiry functions and if you use
expiry-targets to archive your mail the article will go into the
archive and won't get deleted at all".

-- 
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
|            XEmacs - It's not just an editor.             |
|                    It's a way of life.                   |
|------------------------------------<youngs@xemacs.org>---|




  reply	other threads:[~2002-07-11 11:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-09 12:32 Nevin Kapur
2002-07-09 12:56 ` Simon Josefsson
2002-07-09 13:09   ` Nevin Kapur
2002-07-09 13:18     ` Simon Josefsson
2002-07-11 11:36       ` Steve Youngs [this message]
2002-07-26 12:24         ` Simon Josefsson
2002-07-26 15:10           ` Benjamin Rutt
2002-07-26 16:34             ` Simon Josefsson
2002-08-02 10:51           ` Steve Youngs

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=microsoft-free.x465zmts1h.fsf@eicq.dnsalias.org \
    --to=youngs@xemacs.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).