From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/61828 Path: news.gmane.org!not-for-mail From: Katsumi Yamaoka Newsgroups: gmane.emacs.gnus.general Subject: Re: Gnus doesn't update nntp marks files when unplugged Date: Thu, 02 Feb 2006 18:33:07 +0900 Organization: Emacsen advocacy group Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" X-Trace: sea.gmane.org 1138873031 3543 80.91.229.2 (2 Feb 2006 09:37:11 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 2 Feb 2006 09:37:11 +0000 (UTC) Cc: ksinya@quartz.ocn.ne.jp, larsi@gnus.org Original-X-From: ding-owner+m10358@lists.math.uh.edu Thu Feb 02 10:37:09 2006 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from malifon.math.uh.edu ([129.7.128.13]) by ciao.gmane.org with esmtp (Exim 4.43) id 1F4atk-00026e-Np for ding-account@gmane.org; Thu, 02 Feb 2006 10:37:05 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu ident=lists) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 1F4atg-0000az-00; Thu, 02 Feb 2006 03:37:00 -0600 Original-Received: from nas02.math.uh.edu ([129.7.128.40]) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 1F4aqD-0000at-00 for ding@lists.math.uh.edu; Thu, 02 Feb 2006 03:33:25 -0600 Original-Received: from quimby.gnus.org ([80.91.224.244]) by nas02.math.uh.edu with esmtp (Exim 4.52) id 1F4aq7-0004TZ-Ip for ding@lists.math.uh.edu; Thu, 02 Feb 2006 03:33:25 -0600 Original-Received: from washington.hostforweb.net ([66.225.201.13]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1F4aq6-0003fw-00; Thu, 02 Feb 2006 10:33:18 +0100 Original-Received: from [205.234.185.198] (port=50249 helo=mail.jpl.org) by washington.hostforweb.net with esmtpa (Exim 4.52) id 1F4axw-0001AG-Fx; Thu, 02 Feb 2006 03:41:26 -0600 Original-To: ding@gnus.org X-Face: #kKnN,xUnmKia.'[pp`;Omh}odZK)?7wQSl"4o04=EixTF+V[""w~iNbM9ZL+.b*_CxUmFk B#Fu[*?MZZH@IkN:!"\w%I_zt>[$nm7nQosZ<3eu;B:$Q_:p!',P.c0-_Cy[dz4oIpw0ESA^D*1Lw= L&i*6&( User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux) Cancel-Lock: sha1:UGUzqbMaAuFEkJqa5lXP16C4rpQ= X-Hashcash: 1:20:060202:ding@gnus.org::yPEkqhTuT3xkKezK:00000cQY X-Hashcash: 1:20:060202:ksinya@quartz.ocn.ne.jp::SCeJcWZiAPgXgfkt:000000000000000000000000000000000000000fl8 X-Hashcash: 1:20:060202:larsi@gnus.org::MYuYa/3IkxVZaZ46:000000000000000000000000000000000000000000000002Fwf X-Antivirus-Scanner: Clean mail though you should still use an Antivirus X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - washington.hostforweb.net X-AntiAbuse: Original Domain - gnus.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - jpl.org X-Source: X-Source-Args: X-Source-Dir: X-Spam-Score: -2.6 (--) Precedence: bulk Original-Sender: ding-owner@lists.math.uh.edu Xref: news.gmane.org gmane.emacs.gnus.general:61828 Archived-At: --=-=-= ;; I added Lars to Cc:. Does anyone know what is *exceedingly slow*? I'm using only nntp and nnml, moreover am always plugged, so it is hard to imagine what kind of back end slows Gnus down by synchronizing flags. >> 2005-09-20 Lars Magne Ingebrigtsen >> * gnus-agent.el (gnus-agent-synchronize-flags): Switch the >> default to nil, to be able to use Gnus at all. If the default >> switches to something else, then the function should be fixed not >> be exceedingly slow. >> 2004-07-09 Simon Josefsson >> * gnus-agent.el (gnus-agent-synchronize-flags): Revert to ask. >> Users will lose all flag changes made while unplugged with >> e.g. nntp unless flag synchronization happens, thus `nil' is not a >> good default. See numerous reports on ding mailing list. > Katsumi Yamaoka writes: >> IMHO, we should set gnus-agent-synchronize-flags to t by default >> or synchronize at least nntp marks automatically when Gnus is >> re-plugged even if it takes time. I don't know how it is slow >> so far, though. >>>>> In Simon Josefsson wrote: > I agree. I have never found it that slow. It is not disk or network > bound. I read pretty large nntp groups offline, and syncing the flags > doesn't seem to take that long. I don't feel updating nntp marks is slow either. If only the back end which doesn't make it slow is nntp, I can make the following change: --=-=-= Content-Type: text/x-patch Content-Disposition: inline --- gnus-agent.el~ 2006-01-25 07:33:34 +0000 +++ gnus-agent.el 2006-02-02 09:31:37 +0000 @@ -874,8 +874,10 @@ (kill-buffer nil)))) (defun gnus-agent-possibly-synchronize-flags-server (method) - "Synchronize flags for server according to `gnus-agent-synchronize-flags'." - (when (or (and gnus-agent-synchronize-flags + "Synchronize flags for server according to `gnus-agent-synchronize-flags'. +Exceptionally, nntp marks are synchronized with flags unconditionally." + (when (or (memq (car method) '(nntp)) + (and gnus-agent-synchronize-flags (not (eq gnus-agent-synchronize-flags 'ask))) (and (eq gnus-agent-synchronize-flags 'ask) (gnus-y-or-n-p (format "Synchronize flags on server `%s'? " --=-=-=--