From: Tibor Simko <tibor.simko@cern.ch>
To: ding@gnus.org
Subject: Re: latest sources do not client-split IMAP anymore
Date: Thu, 16 Dec 2010 18:21:13 +0100 [thread overview]
Message-ID: <878vzpbpme.fsf@pcuds33.cern.ch> (raw)
In-Reply-To: <m3fwtx8zlk.fsf@quimbies.gnus.org>
On Thu, 16 Dec 2010, Lars Magne Ingebrigtsen wrote:
> That's even more incomprehensible. Your patch just put
>
> (gnus-read-active-file nil nil)
>
> into `gnus-setup-news'.
Yes, `(gnus-read-active-file nil nil)' helps in that place. Note that
it used to be there since 1997, see commit b9299e2.
Maybe the internal function call order during `gnus-setup-news' is
important? If I eval the above after gnus started, then it does not
help anymore. Would you like me to edebug something more concretely?
Best regards
--
Tibor Simko
next prev parent reply other threads:[~2010-12-16 17:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 18:33 Tibor Simko
2010-12-14 22:29 ` Lars Magne Ingebrigtsen
2010-12-15 2:33 ` Tibor Simko
2010-12-15 19:24 ` Lars Magne Ingebrigtsen
2010-12-15 21:11 ` Tibor Simko
2010-12-16 16:13 ` Lars Magne Ingebrigtsen
2010-12-16 17:21 ` Tibor Simko [this message]
2010-12-16 17:25 ` Lars Magne Ingebrigtsen
2010-12-16 21:39 ` Tibor Simko
2010-12-18 20:19 ` Richard Riley
2010-12-20 23:55 ` Tibor Simko
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=878vzpbpme.fsf@pcuds33.cern.ch \
--to=tibor.simko@cern.ch \
--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).