From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Re: [gnus git] branch master updated: =1= gnus-group: fix jump to unknown groups
Date: Sun, 30 Jan 2011 11:20:43 +0100 [thread overview]
Message-ID: <87bp2y8zgk.fsf@topper.koldfront.dk> (raw)
In-Reply-To: <E1Pikya-0007us-00@quimby.gnus.org>
On Fri, 28 Jan 2011 10:50:44 +0100, Julien wrote:
> commit 53a5da8e6cba160eabeff5ff948ebeb78248a6bc
> Author: Julien Danjou <julien@danjou.info>
> Date: Fri Jan 28 10:50:40 2011 +0100
> gnus-group: fix jump to unknown groups
This breaks "create the first nnml-group when starting to use Gnus"
use-case.
If you create a test-user on your system and put some email for him in
/var/mail/$USER and configure Gnus to use nnml, then Gnus won't fetch
any email until you create the first nnml-group (this started around
3595cdc6 and cc7d0e00).
Until your 53a5da8e creating that - now-crucial - first group could be
done by jumping to a nnml-group, after which, Gnus fetches the email
(from ((file))) happily.
With your change, it is impossible for a new user to get email from
/var/mail/$USER as far as I can see?
I guess jump either should revert to the previous behaviour, or it
should allow you to jump to a group if that select method has no groups
at all (so you can create e.g. the first nnml group).
Best regards,
Adam
--
"Här kommer rädslan, gamle vän Adam Sjøgren
När alla fjärilar i magen vaknar upp asjo@koldfront.dk
Viskar välkommen hem"
next parent reply other threads:[~2011-01-30 10:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Pikya-0007us-00@quimby.gnus.org>
2011-01-30 10:20 ` Adam Sjøgren [this message]
2011-01-30 11:30 ` Lars Ingebrigtsen
2011-01-30 11:38 ` Adam Sjøgren
2011-01-31 2:13 ` Scanning methods that don't have any groups (yet) (was: [gnus git] branch master updated: =1= gnus-group: fix jump to unknown groups) Lars Ingebrigtsen
2011-01-31 20:06 ` Scanning methods that don't have any groups (yet) Adam Sjøgren
2011-02-01 2:02 ` Lars Ingebrigtsen
2011-02-01 21:30 ` Adam Sjøgren
2011-02-03 15:37 ` Lars Ingebrigtsen
2011-02-03 18:01 ` Adam Sjøgren
2011-02-03 18:29 ` Adam Sjøgren
2011-02-03 19:49 ` Lars Ingebrigtsen
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=87bp2y8zgk.fsf@topper.koldfront.dk \
--to=asjo@koldfront.dk \
--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).