From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/4392 Path: news.gmane.org!not-for-mail From: =?iso-8859-1?q?S=E9bastien_Kirche?= Newsgroups: gmane.emacs.gnus.user Subject: Re: lost uidvalidity Date: Fri, 28 Jan 2005 11:51:51 +0100 Organization: Aucune. Message-ID: References: Reply-To: =?iso-8859-1?q?S=E9bastien_Kirche?= NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: sea.gmane.org 1138670323 23049 80.91.229.2 (31 Jan 2006 01:18:43 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2006 01:18:43 +0000 (UTC) Original-X-From: nobody Tue Jan 17 17:33:41 2006 Original-Path: quimby.gnus.org!newsfeed1.e.nsc.no!news.tele.dk!news.tele.dk!small.news.tele.dk!proxad.net!freenix!news.cuq.org!not-for-mail Original-Newsgroups: gnu.emacs.gnus Original-NNTP-Posting-Host: 195.25.216.129 Original-X-Trace: yeuse.cuq.org 1106909633 3495 195.25.216.129 (28 Jan 2005 10:53:53 GMT) Original-X-Complaints-To: abuse@cuq.org Original-NNTP-Posting-Date: Fri, 28 Jan 2005 10:53:53 +0000 (UTC) X-Face: ;T}O6aj2o*d:|9po%NCuYvExN3]<#cHr0"FaWCh[}WVn6&@L)YWO'&6AO5Ex:MX=H;.^e}o Td*OaFQEBc_xu%+ChwRl!KK`I'["$^aO1gIN{4OyBdO@1HHD5YO#[kiVCk|/-|mmYnU8yTp+eOv."d 1.G3;ro0Q/`,UY+vY/#5b/{OYxE+X\)tc~p~1vbmZ!o4sciW+e8MW|Pz|nl`l*}]8[#1zQO"]d2*{d wrTKu]5t*Gy_pm3e8o=:(c_ju'zlQ<[oJ|\XjgQQmWZC7S]-Fmp\eBHnBO']/te~/;\@l" D#:h)8Q Cancel-Lock: sha1:G3BSSHQ4g2sAfWhzpLh41byx4ek= User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/21.3.50 (darwin) Original-Xref: bridgekeeper.physik.uni-ulm.de gnus-emacs-gnus:4533 Original-Lines: 19 X-Gnus-Article-Number: 4533 Tue Jan 17 17:33:41 2006 Xref: news.gmane.org gmane.emacs.gnus.user:4392 Archived-At: Le 27 Jan 2005, Simon Josefsson s'est exprimé ainsi : > It is only saved if you quit the group, though. Perhaps C-u 1 RET on > the group, and then q to quit the summary buffer, will help? Too late to test for it. > But I don't believe the uidvalidity group parameter influence header > retrieval, so I think you should look elsewhere for the reason for the > "retrieving headers" message. (Although, arguable, a missing > uidvalidity _should_ lead to a cache invalidate.) I simply copied the value of uidvalidity from my home computer and it seemed to fix that every opening headers retrieving. I hope that i won't have problems with two clients with same uidvalidity... -- Sébastien Kirche