Gnus development mailing list
 help / color / mirror / Atom feed
From: Andrew Cohen <cohen@andy.bu.edu>
To: ding@gnus.org
Subject: deleting articles from search groups?
Date: Sun, 28 Nov 2010 16:17:20 -0500	[thread overview]
Message-ID: <87eia5p2qn.fsf@andy.bu.edu> (raw)

I just added the ability to delete articles directly from an nnir buffer
(similar to moving them). nnir just passes the delete request up the
food chain to the original group holding the article.

But after doing this, I'm wondering whether or not this is a good
idea. Should we worry that someone might be surprised that an action on
the results of a search has the effect of deleting an article
permanently from its original group? But you might say the same thing
about moving articles. 

A secondary question (assuming that allowing deletes is the Right Thing)
is whether or not I've implemented it correctly:) Deleting articles is
done through the 'request-expire-articles function, so I've created one
for nnir. But this means that gnus-summary-expire-articles is called on
the nnir group upon summary-buffer exit. Stepping through this when
exiting an nnir group always shows the list of "expirable" articles as
nil and so no harm is done. Is this guaranteed? I'm guessing that since
nnir is an "ephemeral" group and doesn't really have marks that the list
of expirable articles (gnus-newsgroup-expirable) is always empty?

Andy




             reply	other threads:[~2010-11-28 21:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-28 21:17 Andrew Cohen [this message]
2010-11-28 23:25 ` Dan Christensen
2010-11-29 18:03   ` Sivaram Neelakantan
2010-11-29 18:12     ` Rupert Swarbrick
2010-11-29 18:49       ` Sivaram Neelakantan
2010-11-29  4:28 ` Lars Magne Ingebrigtsen
2010-12-08 15:57   ` Andrew Cohen
2010-12-08 19:25     ` Dan Christensen
2010-12-08 19:31       ` Lars Magne Ingebrigtsen
2010-12-08 19:33         ` Andrew Cohen
2010-12-08 21:44           ` Dan Christensen
2010-12-09 13:21             ` Andrew Cohen
2010-12-08 19:32       ` Andrew Cohen

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=87eia5p2qn.fsf@andy.bu.edu \
    --to=cohen@andy.bu.edu \
    --cc=ding@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).