Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: upgrade notes
Date: Fri, 04 Feb 2011 09:04:40 -0800	[thread overview]
Message-ID: <87y65v91ef.fsf@gnus.org> (raw)
In-Reply-To: <sd7hdf4v96.fsf@wjh.hardakers.net>

Wes Hardaker <wes@hardakers.net> writes:

> + I had (require 'gpg) in my config which I had to remove
>
> + I had an imap-shell-variable that had been customized that pushed a
>   'ssh ... exec imapd' onto the stack.  I don't remember why I had that
>   set up and don't need it any longer, but because the variable no
>   longer existed it broke my config loading.

I'm not sure those can be helped...

> + My folders no longer show which folders have new messages in them.
>   [splitting is done via procmail on the server, and I know the new
>   marks exist there since my running qmailcheck biff window displays
>   properly "new" flagged messages, as did the older gnus version]

That's interesting.  Could you post output from `G E' on one of the
non-updating groups?  And then try `M-g' on the group, and then the `G
E' output again?

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




  reply	other threads:[~2011-02-04 17:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-04 16:31 Wes Hardaker
2011-02-04 17:04 ` Lars Ingebrigtsen [this message]
2011-02-04 17:27   ` Wes Hardaker
2011-02-04 17:42     ` Lars Ingebrigtsen
2011-02-04 20:29       ` Wes Hardaker
2011-02-07 10:25         ` Lars Ingebrigtsen
2011-02-07 16:43           ` Wes Hardaker
2011-02-07 18:37             ` Wes Hardaker
2011-02-07 20:42               ` Eric S Fraga
2011-02-07 21:12                 ` Wes Hardaker
2011-02-06 18:29       ` Reiner Steib
2011-02-07  9:58         ` Lars Ingebrigtsen
2011-02-05 17:07 ` Steinar Bang
2011-02-07 16:45   ` Wes Hardaker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y65v91ef.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).