From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Engster Newsgroups: gmane.emacs.help Subject: Re: Gnus with Emacs 23: gnus-gcc-mark-as-read not working anymore Date: Mon, 05 Oct 2009 17:14:54 +0200 Message-ID: References: <87zl8og1rn.fsf@usenet.my.skamphausen.de> <87eipzto4p.fsf@usenet.my.skamphausen.de> <874oqncbmf.fsf@usenet.my.skamphausen.de> <87zl8e3s7x.fsf@usenet.my.skamphausen.de> <87my4d51iq.fsf@usenet.my.skamphausen.de> <87ljjtetjn.fsf@usenet.my.skamphausen.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1254756281 20920 80.91.229.12 (5 Oct 2009 15:24:41 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 5 Oct 2009 15:24:41 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon Oct 05 17:24:37 2009 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MupOr-0003hV-7A for geh-help-gnu-emacs@m.gmane.org; Mon, 05 Oct 2009 17:22:57 +0200 Original-Received: from localhost ([127.0.0.1]:53311 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MupOr-0002p7-45 for geh-help-gnu-emacs@m.gmane.org; Mon, 05 Oct 2009 11:22:57 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MupOJ-0002nb-Nf for help-gnu-emacs@gnu.org; Mon, 05 Oct 2009 11:22:23 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MupOE-0002kM-6S for help-gnu-emacs@gnu.org; Mon, 05 Oct 2009 11:22:22 -0400 Original-Received: from [199.232.76.173] (port=46732 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MupOE-0002kG-2E for help-gnu-emacs@gnu.org; Mon, 05 Oct 2009 11:22:18 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]:42747) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MupOD-0001vB-B8 for help-gnu-emacs@gnu.org; Mon, 05 Oct 2009 11:22:17 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.50) id 1MupL2-0000VV-20 for help-gnu-emacs@gnu.org; Mon, 05 Oct 2009 17:19:00 +0200 Original-Received: from 134.76.4.38 ([134.76.4.38]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 05 Oct 2009 17:19:00 +0200 Original-Received: from deng by 134.76.4.38 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 05 Oct 2009 17:19:00 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: help-gnu-emacs@gnu.org Original-Lines: 46 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 134.76.4.38 User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.1.50 (darwin) Mail-Copies-To: never Cancel-Lock: sha1:UBt4iMaSveBo6lCY1NlWs/GlhcM= X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:68685 Archived-At: Stefan Kamphausen writes: > ;; Before sending a mail [...] > ;; The other gcc group > (gnus-active "nnml:mail.2009-10") > (1 . 25) > > (gnus-info-read (gnus-get-info "nnml:mail.2009-10")) > ((1 . 25)) > > ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; > ;; Now sending a mail to myself with Gcc-headers like this: > ;; Gcc: nnml:mail.office.all nnml:mail.2009-10 [...] > (gnus-active "nnml:mail.2009-10") > (1 . 25) ; strange? > > (gnus-info-read (gnus-get-info "nnml:mail.2009-10")) > ((1 . 25)) It seems Gnus did not notice yet that a new mail is in in mail.2009-10. Since I cannot reproduce this, I don't know why that happens. You mentioned that you're using the agent; maybe that's the cause of this issue. If you want to further debug this, the best place to start is gnus-inews-do-gcc, where the actual sending happens with the call to gnus-request-accept-article here: (when (or (not (gnus-check-backend-function 'request-accept-article group)) (not (setq group-art (gnus-request-accept-article group method t t)))) (gnus-message 1 "Couldn't store article in group %s: %s" group (gnus-status-message method))) Maybe a (gnus-request-group group nil method) after the sending will force Gnus to update the active information. I'm not sure. Regards, David