From: robert@elastica.com
Cc: ding@ifi.uio.no
Subject: Re: score files...
Date: 11 Aug 1996 20:20:03 -0400 [thread overview]
Message-ID: <fybjl1mj0.fsf@elastica.com> (raw)
In-Reply-To: Jack Vinson's message of 11 Aug 1996 18:16:06 -0400
Jack Vinson <jvinson@cheux.ecs.umass.edu> writes:
>
> >>>>> <robert@elastica.com> writes:
>
> > Actually on further review it looks like comp.lang.java.SCORE matches the
> > entire hierarchy.
>
> Isn't this incorrect? group.SCORE should only match the group in question,
> should it not? group.all.SCORE will match group and any hierarchy under
> group. This is what you wanted, I think.
I think you'll find that isn't the case... I'm not sure if you're saying I'm
wrong or suggesting how it _should_ work..
Anyway,
robert:/export/home/robert/News>ls -al *.SCORE 20:17
-rw-r--r-- 1 robert other 46 Aug 3 18:19 all.SCORE
-rw-r--r-- 1 robert staff 136 Aug 10 21:44 comp.lang.java.SCORE
-rw-r--r-- 1 robert staff 0 Aug 11 20:17 comp.lang.java.all.SCORE
-rw-r--r-- 1 robert staff 223 Aug 11 12:47 comp.lang.perl.SCORE
-rw-r--r-- 1 robert staff 87 Jun 12 21:20 nnfolder:jobs.SCORE
lrwxrwxrwx 1 robert staff 20 Aug 10 19:22 nntp+news:comp.lang.java.SCORE -> comp.lang.java.SCORE
lrwxrwxrwx 1 robert staff 20 Aug 11 12:48 nntp+news:comp.lang.perl.SCORE -> comp.lang.perl.SCORE
(gnus-score-find-bnews "comp.lang.java")
("/export/home/robert/News/comp.lang.java.ADAPT" "/export/home/robert/News/all.SCORE" "/export/home/robert/News/comp.lang.java.SCORE")
(gnus-score-find-bnews "comp.lang.java.misc")
("/export/home/robert/News/comp.lang.java.misc.ADAPT" "/export/home/robert/News/comp.lang.java.all.SCORE" "/export/home/robert/News/comp.lang.java.SCORE" "/export/home/robert/News/comp.lang.java.ADAPT" "/export/home/robert/News/all.SCORE" "/export/home/robert/News/comp.lang.java.misc.SCORE")
>
> This may be related to something I noticed a while back when grokking
> through various 'forsale' groups. There is a forsale.stuff hierarchy and
> various other foo.bar.forsale groups. I thought I was going to need
> forsale.all.SCORE to match the first groups and all.forsale.SCORE to match
> the second groups. It turns out that the former form matches both sets of
> groups. Is this the correct behavior as well?
>
>
> --
> Jack Vinson The Purple Puddle Eater and Captain Jack
> jvinson@cheux.ecs.umass.edu <http://www.cis.upenn.edu/~vinson/home.html>
> Sunderland, MA
> "Skin ain't got no tailored pockets." - Eat _Sell_Me_a_God_
>
--
You are amazed that they exist and they burn so
bright whilst you can only wonder why.
next prev parent reply other threads:[~1996-08-12 0:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-08-10 23:09 robert
1996-08-11 0:33 ` Lars Magne Ingebrigtsen
1996-08-11 15:53 ` robert
1996-08-11 22:16 ` Jack Vinson
1996-08-12 0:20 ` robert [this message]
1996-08-12 4:17 ` Sudish Joseph
1996-08-13 8:20 ` Lars Magne Ingebrigtsen
1996-08-14 1:02 ` score files... [patch] Sudish Joseph
1996-08-11 1:41 ` score files Sudish Joseph
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=fybjl1mj0.fsf@elastica.com \
--to=robert@elastica.com \
--cc=ding@ifi.uio.no \
/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).