"LG" == Lowell Gilbert <[email protected]> writes: ---8<---[snipped 28 lines]---8<--- LG> Even if you invoke Gnus with a startup level that is lower than the LG> level of the newsgroups that it's hanging on? I do this all the LG> time when my news server is unreachable, and it's a two-keystroke LG> solution to the problem...
LG> [I'm assuming you know what group levels are and how to use them, LG> since you aren't questioning that part.] >> And as said groups live somewhere in .newsrc.eld madness I couldn't >> get them out of the way either. LG> That's easy functionality with groups also; you just start Gnus at LG> level zero, so that *no* groups are checked at startup, and then you LG> manipulate the groups from the "*Group*" buffer. Like, setting `gnus-activate-level' or `gnus-activate-foreign-newsgroups' to 0? I'll be sure to test that on the next occasion. I'd be glad to know the two-keystroke-solution though :) [Note: just found `gnus-no-server', doesn't look too bad] But how do you then know which server failed you? Or do you just go through them one-by-one and see which one wouldn't connect? And still, I don't see why gnus can't handle this itself by just giving up on a server after a while and issuing a warning. Remains the lack of portability of the configuration of foreign groups; I'm really missing good old `gnus-export-foreign-groups-to-select-methods'. Or do people actually use [[info:gnus:Slave%20Gnusae][Slave Gnusae]] ? I found the concept rather confusing and I'm not quite sure how to implement this to achieve consistency on multiple machines. -- Philipp Haselwarter _______________________________________________ info-gnus-english mailing list [email protected] http://lists.gnu.org/mailman/listinfo/info-gnus-english
