From: Mike Ballard <dont_w@nt_spam.org>
Subject: Re: searching groups buffer
Date: Thu, 20 May 2004 00:48:28 GMT [thread overview]
Message-ID: <m2pt8zna0x.fsf@west_f1.net> (raw)
In-Reply-To: <v9zn84zpnp.fsf@marauder.physik.uni-ulm.de>
On Wed May 19, Reiner Steib disturbed my nap when he said:
> On Tue, May 18 2004, Mike Ballard wrote:
>
> > I'm not sure which vars to include (if needed) but my groups buffer is a
> > collapsable, hierachical listing of groups I'm subscribed to. I notice
> > that when I do C-s only branches that aren't collapsed return hits
> > (collapsed branches which contain a hit in them are not seen). Is there a
> > way to get search to check collapsed branches?
>
> I'm not sure if I understand your problem. Isn't `j'
> (gnus-group-jump-to-group) sufficient?
>
I wanted to include (but didn't know which) an appropriate var which
specifies the appearance of my groups buffer to explain that my subscribed
groups are clustered under headings inside subheadings (it's been so long
I don't know, this may be the default that everyone sees). I only have a
couple group heading/subheading threads opened at any one time meaning
most subscribed groups are 'hidden' inside the other collapsed headings.
Often it's not easy remembering which collapsed heading/subheading
contains a subscribed group I'm looking for.
"j" is a great cmd (that I didn't know about) and does just what I want
except that it requires spelling out the entire group name. Something
such as C-s is what I was hoping for (to hit on partial spellings).
Mike
--
mikeballard at symbol verizon period net
"If your main parachute fouls, deploy your reserve. If your reserve is
also fouled, you have the rest of your life to get it straightened out."
prev parent reply other threads:[~2004-05-20 0:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m23c5xic9a.fsf@west_f1.net>
2004-05-19 10:18 ` Reiner Steib
2004-05-20 0:48 ` Mike Ballard [this message]
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=m2pt8zna0x.fsf@west_f1.net \
--to=dont_w@nt_spam.org \
/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).