Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai Grossjohann <grossjohann@charly.cs.uni-dortmund.de>
Cc: ding@gnus.org
Subject: Re: nnfolder question
Date: 05 Aug 1997 20:16:16 +0200	[thread overview]
Message-ID: <vaf3eooebrj.fsf@ls6.cs.uni-dortmund.de> (raw)
In-Reply-To: Greg Thompson's message of "05 Aug 1997 13:42:19 -0400"

>>>>> On 05 Aug 1997, Greg Thompson said:

  Greg> now some questions: can i have groups in subdirectories to make a
  Greg> heirarchy of saved mail files?

,----- C-h v gnus-use-long-file-name RET
| gnus-use-long-file-name's value is nil             
|                                                    
| 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.
`-----

I think setting this variable to nil will make the group foo.bar
reside in the file foo/bar.  I've only used this with nnml groups, and
there nnml:foo.bar is a directory ~/Mail/foo/bar.

kai
-- 
Signature?  What signature?


      reply	other threads:[~1997-08-05 18:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-08-05 17:42 Greg Thompson
1997-08-05 18:16 ` Kai Grossjohann [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=vaf3eooebrj.fsf@ls6.cs.uni-dortmund.de \
    --to=grossjohann@charly.cs.uni-dortmund.de \
    --cc=ding@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).