Hi Michael, > I have no clue, really, but it sounds like this could help: > > (info "(gnus) Changing Servers") > > In particular 'gnus-group-clear-data' is maybe what you should do. You > can make a backup of your data (.newsrc) and, yeah, maybe that's already > the best you can do. > > I don't know how Gnus assigns article numbers, but maybe those numbers > are invalid in your case anyway (sounds a bit like it).
`gnus-group-clear-data-on-native-groups' didn't change much, and my .newsrc is -- and has always been -- empty. Luckily, I did have a backup, so I didn't lose much at all. But here is something interesting. I hope people will correct me if I'm wrong. I looked into gnus-sum.el, and it appeared that GNUS does everything in terms of article numbers. If they are wrong, that's a wrap. In particular, line 5879 says (range-uncompress (gnus-active group)) This line *does* get executed since, in my setup, `gnus-newsgroup-maximum-articles' is nil. This line outputs a list with the article numbers in that group. All subsequent calculations are done in terms of that list. The net result is that, in the GNUS world, having the articles nicely ordered by default is a privilege rather than a right. If the right is not granted, one can still achieve this by, say, running G G date:..today limit:200 Also, I was not changing servers. All I did was remove the --pull from mbsync --pull gmail and things went haywire. GNUS was busy-waiting endlessly, trying to absorb the new Maildir.
