From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/6181 Path: main.gmane.org!not-for-mail From: Mark Borges Newsgroups: gmane.emacs.gnus.general Subject: unticking ticked articles in nnml groups Date: Wed, 8 May 1996 12:33:37 -0600 Organization: CIRES, University of Colorado Message-ID: <199605081833.MAA06505@roberts.cdc.noaa.gov> NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035146674 2795 80.91.224.250 (20 Oct 2002 20:44:34 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 20:44:34 +0000 (UTC) Return-Path: ding-request@ifi.uio.no Original-Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by deanna.miranova.com (8.7.5/8.6.9) with SMTP id MAA06077 for ; Wed, 8 May 1996 12:39:18 -0700 Original-Received: from cdc.noaa.gov (manager.Colorado.EDU [128.138.218.210]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) id for ; Wed, 8 May 1996 20:35:31 +0200 Original-Received: from roberts by cdc.noaa.gov (SMI-8.6/SMI-SVR4) id MAA23980; Wed, 8 May 1996 12:35:08 -0600 Original-Received: by roberts (SMI-8.6) id MAA06505; Wed, 8 May 1996 12:33:37 -0600 Original-To: Ding Gnus List X-Attribution: mb Xref: main.gmane.org gmane.emacs.gnus.general:6181 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:6181 In all liklihood this is working as it should, but I find it somewhat counter-intuitive... Suppose I tick, `!', a bunch of articles in an nnml group. After a few months, the number of ticked articles in the nnml group is overwhelming (apparently I err on the side of interesting ;-). I then go back and mark as read, via `d', bound to gnus-summary-mark-as-read-forward(), all the articles that weren't so interesting after all. I thought Gnus would then mark them as expirable and thus subject them to the expiry process, but it doesn't. It marks them as old, `O', and does not expire them. Shouldn't they go back to expirable, `E'? After all, when I read an article it gets marked as expirable (I don't recall if this is an option or not right now), and if the article has been ticked it most likely has been read (yes, I can think of a situation where that assumption would be false, though). Alternatively, could I rebind `d' to a homegrown gnus-mark-as-expirable-forward() (i.e., the complement of gnus-mark-as-read-forward()) and not suffer any ill consequences in other groups? For me, cap-E is hard to type and I want it to move forward after changing the mark. What do others think? Is the current behavior the desired one? If so, is there some option (or group of options) that will give me my desired behavior? Right now I go back and change all the `O' marks to `E' so that the articles will eventually get deleted, but I'm getting tired of doing that. I bet there is a better way in sgnus to get done what I want. Thanks for any help or comments. -- -mb-