Re: Some useful key bindings

[Ted Zlatanov]

On Wed, 06 Jan 2010 16:53:20 +0100 Cecil Westerhof <Cecil@decebal.nl> wrote: 

CW> Ted Zlatanov <tzz@lifelogs.com> writes:
CW> Did not even think about that, but maybe that is not a bad idea. Maybe
CW> it should be made even more general. I think it would be useful to have
CW> more as a compact and a important list. And it would be nice if you do
CW> not have to edit your .gnus for this. But then the topics have to be
CW> saved somewhere. What is the best way to do this?
>> 
>> The topics are already saved in the Gnus newsrc.eld file.  You just need
>> to associate a numeric level with a topic, which Gnus can do as a topic
>> property and save it automatically (see gnus-topic-edit-parameters, 
>> `G p' in the *Group* buffer).  Simply, gnus-group-set-current-level (`S l')
>> needs to be adapted to handle topics as well.
>> 
>> Once that's done, your commands can become filters on the full topic
>> list based on each topic's level.

CW> Not quite, I want to work with names. For two reasons: it is clearer and
CW> I can think of a situation in which topic A should be visible in
CW> situation I and topic B not and topic B should be visible in situation
CW> II and topic A not. This can not be solved in your case, but it can in
CW> mine.

You can make the topic subscription level a list of strings
(effectively, tags).  I encourage you to work with topic parameters
because configuring and storing them is already done by Gnus.  With the
external approach you'll be doing more work and it won't integrate with
Gnus as well.

Ted