From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Scanning methods that don't have any groups (yet) (was: [gnus git] branch master updated: =1= gnus-group: fix jump to unknown groups)
Date: Sun, 30 Jan 2011 18:13:56 -0800 [thread overview]
Message-ID: <87aaihlt0b.fsf_-_@gnus.org> (raw)
In-Reply-To: <87y6627has.fsf@topper.koldfront.dk>
asjo@koldfront.dk (Adam Sjøgren) writes:
> I tried some monkeying around with the changes in/around those two
> commits, but I didn't quite get anywhere before I got distract... Oooh,
> look, shiny!
I think I may now have fixed this problem, but this area is, er, subtle,
so there may be unintended negative consequences...
>> I think there's supposed to be a variable somewhere saying whether it's
>> possible to jump to a group that doesn't exist (yet). I certainly think
>> it should be possible to jump to groups that Gnus don't know about.
>
>> So I think the patch should possibly be reverted.
>
> Super.
I've now done so.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2011-01-31 2:13 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 ` Lars Ingebrigtsen [this message]
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=87aaihlt0b.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).