Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Subject: Finding all score files . . .
Date: 16 Mar 1998 07:38:58 -0800	[thread overview]
Message-ID: <m3iupe4pd9.fsf@org.com> (raw)


First let me thank every one for the tips and gentle reminders to RTFM
in he previous thread on down scoring.

I guess I counted myself in the group Lars graciously calls "Casual users"
  >  Casual users are not expected to edit these files;
  > everything can be changed from the summary buffer.

Only problem, I went a step farther and didn't read the section either....


On another subject:  Lets see if I have this much right:

It is necessary to run gnus with long file names set to nil if you want
to use gnus-agent stuff off-line.  This is not yet fixed to where you
can run gnus in long file name 't' and still use agent successfully.

If I am right about the above then a certain problem arises when, gnus
is freshly started and you open the first group.  Gnus shows a message 
"Findin all score files . . . " and with the ridiculously deeply layered
file structure produced in no-long-file-name mode, it can be quite
a wait while gnus ruffles the HDD looking for the score files.

I have seen as long as 15 to 20 seconds (sounds short here but seems
long when you are bringing up a group)


Is there a path to the search gnus follows for this?  Could a user maybe
put symlinks to the score files in the first directory searched and have
a variable where you could tell gnus to search no further. (or something
similar)


Or better yet have gnus put all score files in one SCORE directory and
the first line of each file would tell gnus what group it went with.

-- 

Harry Putnam  reader@newsguy.com


             reply	other threads:[~1998-03-16 15:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-03-16 15:38 Harry Putnam [this message]
1998-03-19 13:24 ` Lars Magne Ingebrigtsen
1998-03-21 16:39   ` Harry Putnam
1998-03-23 13:17     ` Lars Magne Ingebrigtsen
1998-03-24  2:16       ` Harry Putnam
1998-03-24 10:16         ` Lars Magne Ingebrigtsen

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=m3iupe4pd9.fsf@org.com \
    --to=reader@newsguy.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).