Setting gnus-list-identifiers on a per-group basis

Setting gnus-list-identifiers on a per-group basis

[Paul Moore]

I have

    (setq gnus-list-identifiers '("\\[[^]]*\\]" "(Fwd)" "AW:"))

in my .gnus.el, in order to strip [list-id] junk from the start of
subject lines. However, I have a newsgroup (rec.games.roguelike.angband)
where [xx] is used for a useful subject convention, so I'd like to set
gnus-list-identifiers to just '("(Fwd)" "AW:") in that group.

I tried G c to customize the group parameters, and set

    Variables:
    Set variables local to the group you are entering. *
    [INS] [DEL] Variable: gnus-list-identifiers
                Value: '("(Fwd)" "AW:")

When I go into the summary buffer and do C-H v, I see that
gnus-list-identifiers has the value I specified as a buffer-local
value, but the summary reflects the global value.

Should I be setting this differently? Is it a timing issue (the
group-specific value not being set until after the summary has been
generated)?

Thanks,
Paul Moore.

Re: Setting gnus-list-identifiers on a per-group basis

[Paul Jarc]

Paul Moore <gustav@morpheus.demon.co.uk> wrote:
>     Variables:
>     Set variables local to the group you are entering. *
>     [INS] [DEL] Variable: gnus-list-identifiers
>                 Value: '("(Fwd)" "AW:")
>
> When I go into the summary buffer and do C-H v, I see that
> gnus-list-identifiers has the value I specified as a buffer-local
> value, but the summary reflects the global value.

Try also adding gnus-list-identifiers to gnus-newsgroup-variables.


paul

Re: Setting gnus-list-identifiers on a per-group basis

[Jesper Harder]

Paul Moore <gustav@morpheus.demon.co.uk> writes:

> I did some searching around, and had a go. The upgrade was pretty
> painless in the end. But I'm still not particularly clear as to what's
> new. The manual doesn't include a "New features in Oort Gnus" section,
> as far as I can tell, and I can't see a News file with any sort of
> summary.

Look for the file 'GNUS-NEWS' in the top directory of the Gnus
distribution.

> Also, when I tried to format the manual for printing, I got errors
> (undefined control sequence @iflatex). This is using texi2dvi (both
> for DVI and PDF output) and using "raw" (PDF)LaTeX and TeX. (The
> latest versions from the MikTeX distribution for Windows).

Yes, you have to use the makefile to generate the dvi version.  If you
have cygwin, it might work on Windows.

Otherwise I think something like this

     emacs gnus.texi -l infohack.el -f infohack-remove-unsupported

should give you a version, which can be processed with texi2dvi.