From: Lloyd Zusman <ljz@asfast.com>
Subject: Re: Group-specific gnus-auto-select-next? (was: Another Oort error.)
Date: 30 Sep 2001 18:17:13 -0400 [thread overview]
Message-ID: <m2ite0tjbq.fsf@asfast.com> (raw)
In-Reply-To: <vafofp9epfi.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Tue, 21 Aug 2001 11:24:17 +0200")
I'm sorry I took so long to reply to you. Your response arrived when
I was out of town, and I had a lot of work to make up when I got back.
Then, the WTC was bombed in my city, and only now am I catching up
with everything.
I'm replying here, in case anyone might find this information useful.
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Lloyd Zusman <ljz@asfast.com> writes:
>
>> Here it is:
>>
>> ;; Wrap `gnus-summary-read-group' so that `gnus-auto-select-next'
>> ;; gets set according to `no-auto-select-pattern'
>>
>> (defadvice gnus-summary-read-group (around gnus-summary-read-group freeze)
>> [ ... etc. ... ]
>>
>> I did this because it seemed at the time that there was no other way
>> to selectively set `gnus-auto-select-next' based upon the name of the
>> newsgroup. [ ... ]
>
> Hm. Does it work to set a local variable in the group parameters?
>
> (setq gnus-parameters '(("e" (gnus-auto-select-next t))
> ("" (gnus-auto-select-next nil))))
>
> Maybe this sets it to t for all group names with e in them.
I tried this, and indeed it works.
Thank you very much.
> kai
> --
> Symbol's function definition is void: signature
--
Lloyd Zusman
ljz@asfast.com
next prev parent reply other threads:[~2001-09-30 22:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-20 2:33 Another Oort error Lloyd Zusman
2001-08-20 11:03 ` Lars Magne Ingebrigtsen
2001-08-21 2:02 ` Group-specific gnus-auto-select-next? (was: Another Oort error.) Lloyd Zusman
2001-08-21 9:24 ` Kai Großjohann
2001-09-30 22:17 ` Lloyd Zusman [this message]
2001-10-01 1:31 ` I lied (Was: Group-specific gnus-auto-select-next?) Lloyd Zusman
2001-10-01 9:39 ` Kai Großjohann
2001-10-01 10:27 ` Lloyd Zusman
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=m2ite0tjbq.fsf@asfast.com \
--to=ljz@asfast.com \
/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).