From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Michael Welsh Duggan Newsgroups: gmane.emacs.devel Subject: Re: gnus-summary-tick-article-forward doesn't work any more? Date: Thu, 14 Dec 2006 02:10:55 -0500 Message-ID: <873b7j0x6o.fsf@cs.cmu.edu> References: <87u00ctuhc.fsf@stupidchicken.com> <87wt58qhl1.fsf@cs.cmu.edu> <87slfno4c5.fsf@stupidchicken.com> NNTP-Posting-Host: dough.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1166080297 6369 80.91.229.10 (14 Dec 2006 07:11:37 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 14 Dec 2006 07:11:37 +0000 (UTC) Cc: emacs-devel@gnu.org, Stefan Monnier , bugs@gnus.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Dec 14 08:11:36 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by dough.gmane.org with esmtp (Exim 4.50) id 1Gukkf-0000xq-3O for ged-emacs-devel@m.gmane.org; Thu, 14 Dec 2006 08:11:33 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Gukke-00019W-IJ for ged-emacs-devel@m.gmane.org; Thu, 14 Dec 2006 02:11:32 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GukkR-00016x-NU for emacs-devel@gnu.org; Thu, 14 Dec 2006 02:11:19 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GukkP-00015q-GM for emacs-devel@gnu.org; Thu, 14 Dec 2006 02:11:18 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GukkP-00015n-AV for emacs-devel@gnu.org; Thu, 14 Dec 2006 02:11:17 -0500 Original-Received: from [205.201.10.244] (helo=maru) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1GukkP-0006Mr-1o for emacs-devel@gnu.org; Thu, 14 Dec 2006 02:11:17 -0500 Original-Received: from md5i by maru with local (Exim 4.63) (envelope-from ) id 1Gukk4-0007cr-0s; Thu, 14 Dec 2006 02:10:56 -0500 Original-To: Chong Yidong In-Reply-To: <87slfno4c5.fsf@stupidchicken.com> (Chong Yidong's message of "Sun\, 10 Dec 2006 15\:58\:50 -0500") User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.91 (gnu/linux) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:63704 Archived-At: Chong Yidong writes: > Can we get this thread moving again? > >>>>> Recently I started to notice ticks being dropped in Gnus. I first thought >>>>> that maybe my IMAP server had changed and didn't allow tick marks any more >>>>> (I access my IMAP server from a few different computers so if a tick is only >>>>> recorded in the .newsrc rather than on the IMAP server it will appear to >>>>> have been lost when I read my email from the other machine). >>> >>>> I haven't seen this bug, and I also use Gnus imap with heavy use of >>>> ticks. Is it still happening to you? >>> >>> Yes. And even the unread status gets dropped: if I reproduce the same >>> steps as in the original report but instead of ticking with ! and use M-u to >>> mark it as unread, the same thing happens: the unseen status gets lost as >>> soon as I leave the group and try to re-enter it. >>> As mentioned, this doesn't happen with all messages, but I can still >>> reproduce it with the same message and I know it happened with others >>> as well. [...] > Michael Welsh Duggan wrote: >> >> First: are you running the server in agent mode? In the *Server* >> buffer (reach using `^' in group buffer), does the server you are >> using have "(agent)" by it? I have had similar problems in the past >> when accidentally using the server in agent mode when I had no >> reason to do so. I would like to note that Stefan Monnier let me know that turning off agent mode for the IMAP server did (at least temporarily) solve the problem. This, of course, does not solve the root of the problem. I suspect that the agent data stored in ~/News/agent gets corrupted, and everything after that goes wonky. -- Michael Welsh Duggan (md5i@cs.cmu.edu)