From: Lloyd Zusman <ljz@asfast.com>
Subject: Group-specific gnus-auto-select-next? (was: Another Oort error.)
Date: 20 Aug 2001 22:02:49 -0400 [thread overview]
Message-ID: <m2bsla41bq.fsf_-_@asfast.com> (raw)
In-Reply-To: <m3bslbdmdj.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Mon, 20 Aug 2001 13:03:20 +0200")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Lloyd Zusman <ljz@asfast.com> writes:
>>
>> [...]
>>
>> ad-Orig-gnus-summary-read-group-around-gnus-summary-read-group(
>> "alt.language.spanish" nil nil nil nil nil nil)
>
> You have this function defadviced, it looks like. Could that be the
> problem?
Oh yeah ... I did that ages ago and forgot about it. But why would
that be causing a problem after working fine for many months? It's a
pretty simple defadvice.
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)
ad-do-it
(setq gnus-auto-select-next
(not (and gnus-newsgroup-name
(string-match no-auto-select-pattern
gnus-newsgroup-name)))))
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. I tried all the hooks (yes, I really did try *all* of
them), but none of them could be used to cause the
`gnus-auto-select-next' setting to be recognized and acted upon in a
group-specific manner. And I tried lots of other things as well,
before finally giving up and using the defadvice.
But this was a long time ago. Perhaps now is there a way to do this,
after all?
Thanks in advance.
--
Lloyd Zusman
ljz@asfast.com
next prev parent reply other threads:[~2001-08-21 2:02 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 ` Lloyd Zusman [this message]
2001-08-21 9:24 ` Group-specific gnus-auto-select-next? (was: Another Oort error.) Kai Großjohann
2001-09-30 22:17 ` Lloyd Zusman
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=m2bsla41bq.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).