From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: gnus-use-long-filenames
Date: 29 Mar 1998 11:58:56 +0200 [thread overview]
Message-ID: <m3ogypvmvz.fsf@sparky.gnus.org> (raw)
In-Reply-To: Harry Putnam's message of "27 Mar 1998 20:45:25 -0800"
Harry Putnam <reader@newsguy.com> writes:
> My understanding is that in order to use 'agent' successfully,
> gnus-use-long-filenames must be set to 'nil'
No, that shouldn't be necessary. (Well, there isn't such a variable,
but there is `gnus-use-long-file-name', which I guess is what you
mean.)
> I understand from snippets and hints from Lars, that this can be
> arranged where the score files are in long file name format. Making
> this search take considerable less time. And further that this is
> explained somewhere in the Gnus Info.
`C-h v' is your friend:
---------
gnus-use-long-file-name's value is t
Documentation:
*Non-nil means that the default name of a file to save articles in is the group name.
If it's nil, the directory form of the group name is used instead.
If this variable is a list, and the list contains the element
`not-score', long file names will not be used for score files; if it
contains the element `not-save', long file names will not be used for
saving; and if it contains the element `not-kill', long file names
will not be used for kill files.
Note that the default for this variable varies according to what system
type you're using. On `usg-unix-v' and `xenix' this variable defaults
to nil while on all other systems it defaults to t.
----------
So if you set this to `(not-score)', you'll get long file names for
everything but score files, which is the opposite of what you want. :-)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1998-03-29 9:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-28 4:45 gnus-use-long-filenames Harry Putnam
1998-03-29 9:58 ` Lars Magne Ingebrigtsen [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=m3ogypvmvz.fsf@sparky.gnus.org \
--to=larsi@gnus.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).