Re: No Gnus v0.13 is released

[Lars Ingebrigtsen <larsi@gnus.org>]

Jeremy Hankins <nowan@nowan.org> writes:

> I haven't been following the (bleeding?) edge, so this is a big jump for
> me.  I apologize if I haven't rtfm'd adequately, but after the switch
> the message read status seems to be stored locally rather than on the
> IMAP server, or something.  I've got multiple machines running gnus
> which all connect to the same IMAP server, but they're all suddenly
> showing tons of unread messages, which I have read.

Hm.  The first time you use the new Gnus, it should do a complete resync
of all the article marks from the IMAP server.

Hm...  ah, I think I now understand why that fails.  It only does the
complete resync in the non-QRESYNC case.  The QRESYNC code has been
added later, and doesn't have the proper logic to avoid doing that the
very first time.

I've now pushed out something I think should fix this.

> Other (minor) issues I've run into during the switch:
>
>  - I had to replace gnus-user-date-format-alist with
>    gnus-summary-user-date-format-alist

Oh, it's a user-visible variable?  I've now renamed it back to
gnus-user-date-format-alist.

>  - the %U format in gnus-group-line-format doesn't seem to be working --
>    I haven't done a lot of troubleshooting but it looks like it's
>    returning a number instead of a string.  For now I've done the
>    quick-and-dirty thing of using a user-format-function.

Hm...  it seems to work for me.  What does %U display for you?

>  - Gnus failed to start for me until I disabled diminish for
>    gnus-agent-mode.  Not a gnus problem, obviously, but it took me a
>    while to realize what was going on.

What's diminish?

> On the plus side: Wow, blazing fast updates!  With multiple imap sources
> and nntp I suspect that the asynchronous connection helps a lot, but the
> improvement is dramatic whatever the source.

Great!  Nice to hear that.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen