From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Re: Scanning methods that don't have any groups (yet)
Date: Mon, 31 Jan 2011 21:06:03 +0100 [thread overview]
Message-ID: <87mxmgu9ck.fsf@topper.koldfront.dk> (raw)
In-Reply-To: <87aaihlt0b.fsf_-_@gnus.org>
On Sun, 30 Jan 2011 18:13:56 -0800, Lars wrote:
> I think I may now have fixed this problem, but this area is, er, subtle,
> so there may be unintended negative consequences...
It didn't seem to work in my test:
* Create a new $USER
* Send an email to him, stored in /var/mail/$USER
* Configure .gnus with: (setq gnus-select-method '(nnnil "")
gnus-secondary-select-methods '((nnml "")))
* Start Gnus.
* Try g. Try F. Try g. Nah.
The email stays in /var/mail/$USER until I:
* j nnml:something, then u on the group, then g. Yes.
>>> So I think the patch should possibly be reverted.
[...]
> I've now done so.
That part, jumping to an unknown group, worked fine now, again.
Best regards,
Adam
--
"My ethicator machine must've had a built-in moral Adam Sjøgren
compromise spectral release phantasmatron!" asjo@koldfront.dk
next prev parent reply other threads:[~2011-01-31 20:06 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 ` [gnus git] branch master updated: =1= gnus-group: fix jump to unknown groups Adam Sjøgren
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 ` Adam Sjøgren [this message]
2011-02-01 2:02 ` Scanning methods that don't have any groups (yet) 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=87mxmgu9ck.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).