From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chong Yidong Newsgroups: gmane.emacs.devel Subject: Re: gnus-summary-tick-article-forward doesn't work any more? Date: Sun, 10 Dec 2006 15:58:50 -0500 Message-ID: <87slfno4c5.fsf@stupidchicken.com> References: <87u00ctuhc.fsf@stupidchicken.com> <87wt58qhl1.fsf@cs.cmu.edu> NNTP-Posting-Host: dough.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1165784344 31688 80.91.229.10 (10 Dec 2006 20:59:04 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 10 Dec 2006 20:59:04 +0000 (UTC) Cc: bugs@gnus.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Dec 10 21:58:57 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 1GtVlB-0001jm-3X for ged-emacs-devel@m.gmane.org; Sun, 10 Dec 2006 21:58:57 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GtVlA-00025f-8D for ged-emacs-devel@m.gmane.org; Sun, 10 Dec 2006 15:58:56 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GtVkz-00025a-9E for emacs-devel@gnu.org; Sun, 10 Dec 2006 15:58:45 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GtVkx-00025O-Nq for emacs-devel@gnu.org; Sun, 10 Dec 2006 15:58:43 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GtVkx-00025L-IZ for emacs-devel@gnu.org; Sun, 10 Dec 2006 15:58:43 -0500 Original-Received: from [18.19.1.138] (helo=cyd.mit.edu) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GtVkx-0001m4-M7 for emacs-devel@gnu.org; Sun, 10 Dec 2006 15:58:43 -0500 Original-Received: by cyd.mit.edu (Postfix, from userid 1000) id E27E64E458; Sun, 10 Dec 2006 15:58:50 -0500 (EST) Original-To: Michael Welsh Duggan , Stefan Monnier In-Reply-To: <87wt58qhl1.fsf@cs.cmu.edu> (Michael Welsh Duggan's message of "Mon\, 04 Dec 2006 01\:51\:38 -0500") User-Agent: Gnus/5.11 (Gnus v5.11) 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:63551 Archived-At: 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. Stefan, if you can reproduce this bug easily, can you try binary-searching through old Emacs/Gnus versions and identify which recent checkin (if any) caused the problem to occur? Also, see if the problem happens with other IMAP servers, if possible? 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. > > Also, could you set `imap-debug' to t, reproduce the problem, and send the > contents (or partial contents) of the *imap-debug* buffer? There was a trace in the original bug report: http://lists.gnu.org/archive/html/emacs-devel/2006-11/msg01227.html