From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/68065 Path: news.gmane.org!not-for-mail From: Lloyd Zusman Newsgroups: gmane.emacs.gnus.general Subject: Re: Automatically marking Gcc's as SEEN in nnimap Date: Sun, 04 Jan 2009 20:40:57 -0500 Organization: Take a hippopotamus to lunch today. Message-ID: References: <877i5zyw2o.fsf@gmail.com> <84ljuecjdi.fsf@incoming.verizon.net> <87prj49ugi.fsf@randomsample.de> <87mye8t1zr.fsf@engster.org> <87d4f2py1o.fsf@randomsample.de> <874p0epqth.fsf@randomsample.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1231119727 30450 80.91.229.12 (5 Jan 2009 01:42:07 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 5 Jan 2009 01:42:07 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M16510@lists.math.uh.edu Mon Jan 05 02:43:17 2009 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.50) id 1LJeUu-0000bJ-AQ for ding-account@gmane.org; Mon, 05 Jan 2009 02:43:16 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1LJeSu-0002AQ-Lv; Sun, 04 Jan 2009 19:41:12 -0600 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1LJeSs-0002AA-Ty for ding@lists.math.uh.edu; Sun, 04 Jan 2009 19:41:10 -0600 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtp (Exim 4.69) (envelope-from ) id 1LJeSq-0000Ds-2Z for ding@lists.math.uh.edu; Sun, 04 Jan 2009 19:41:10 -0600 Original-Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by quimby.gnus.org with esmtp (Exim 3.36 #1 (Debian)) id 1LJeT6-0002DW-00 for ; Mon, 05 Jan 2009 02:41:24 +0100 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1LJeSq-0006ov-5i for ding@gnus.org; Mon, 05 Jan 2009 01:41:08 +0000 Original-Received: from 209.59.210.144 ([209.59.210.144]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 05 Jan 2009 01:41:08 +0000 Original-Received: from ljz by 209.59.210.144 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 05 Jan 2009 01:41:08 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 45 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 209.59.210.144 User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.60 (darwin) Cancel-Lock: sha1:Wb8Bm5pUlNY0Fhkm/W3eebotidY= Cache-Post-Path: purity-of-essence.net!unknown@nadie.us X-Cache: nntpcache 3.0.2 (see http://www.nntpcache.com/) X-Spam-Score: -1.5 (-) List-ID: Precedence: bulk X-Spam-Report: 5.7 points; * 1.7 SUBJ_AS_SEEN Subject contains "As Seen" * 0.0 RCVD_BY_IP Received by mail server with no name * 4.0 RCVD_NUMERIC_HELO Received: contains an IP address used for HELO Xref: news.gmane.org gmane.emacs.gnus.general:68065 Archived-At: David Engster writes: > Lloyd Zusman writes: >> >> [ ... ] >> >> Furthermore, immediately after this command completes, the articles seem >> to be marked as SEEN (or at least they are not flagged as unread/unseen >> in the *Summary* buffer). However, if I then run a >> `gnus-group-get-new-news', the unread/unseen mark returns, and I can >> only make it go away by actually reading the article. > > I would guess this behavior comes from gaps in the article numbers. This > problem can't currently properly dealt with and also depends on the used > IMAP server. Does doing M-g on that group fix the number? Yes, `M-g' fixes it. >> [ ... ] > > No, they don't get re-propagated to the IMAP server. Gnus simply doesn't > have all the necessary information for correctly calculating the number > of unread articles. When you do gnus-group-get-new-news, Gnus will try > to determine the number of unread articles purely based on the active > information (ie. lowest and highest article number in a group), and on > the group info, which contains the article numbers of already seen > articles. When you do M-g on a group, it will also re-scan the group on > the server, which can sometimes correct this problem. OK. This explains and fixes the problem. So do you see any disadvantage to my writing some function that runs `gnus-group-get-new-news-this-group' (`M-g') on each of my groups, and then rebinding this function to `g' (currently bound to `gnus-group-get-new-news')? It seems like such a function would be more useful, especially for nnimap groups. In any case, thanks for all your help! -- Lloyd Zusman ljz@asfast.com God bless you.