Gnus development mailing list
 help / color / mirror / Atom feed
From: John Turner <turner@xdiv.LANL.GOV>
Cc: ding@ifi.uio.no, xemacs-beta@xemacs.org
Subject: Re: Gnus 5.2.20: SAVEDIR
Date: Thu, 20 Jun 1996 08:18:05 -0600	[thread overview]
Message-ID: <199606201418.IAA10828@gielgud.lanl.gov.xdiv> (raw)
In-Reply-To: <vk20jb0zc8.fsf@cdc.noaa.gov>

Mark Borges writes:
 > >> On Wed, 19 Jun 1996 23:15:14 -0600,
 > >> John Turner(JT) wrote:
 > [...]
 > JT> The problem is that once again gnus-directory isn't being set to
 > JT> the value of the env. var. SAVEDIR as it should be:
 > 
 > JT> gielgud.lanl.gov% echo $SAVEDIR 
 > JT> /home/turner/Mail/News 
 > 
 > JT> C-h v gnus-directory:
 > JT> gnus-directory's value is "~/News/" 
 > 
 > I hate it when that happens.
 > 
 > What *should* work according to my understanding of the
 > `gnus-directory' documentation is to
 > 
 >    (setq gnus-directory "/my/news/path/")
 > 
 > in your gnus-init-file. But it doesn't, because all the other Gnus
 > file variables the doc-string talks about:
 > 
 > ------------------------------------------------------------
 > gnus-directory's value is "/home/mdb/Mail/news"
 >   -- a variable declared in Lisp.
 > 
 > Documentation:
 > *Directory variable from which all other Gnus file variables are
 > derived.
 > ------------------------------------------------------------
 > 
 > have already been set by the time gnus-init-file is read. So, for
 > example, you wind up with gnus-article-save-directory still pointing
 > at the default ("~/News"). And then bad things happen.
 > 
 > The obvious fix it to have `gnus-init-file' be read earlier on in
 > gnus.el, but I don't know if there are any side-effects to doing
 > this.
 > 
 > The only way I've been able to get what I want is the ugly gross way:
 > manually set each of these in my gnus-init-file, e.g.,
 > ------------------------------------------------------------
 > (setq
 >  gnus-directory (expand-file-name "~/Mail/news")
 >  gnus-nocem-directory (expand-file-name "~/Mail/news/NoCeM/")
 >  gnus-article-save-directory gnus-directory
 >  gnus-kill-files-directory gnus-directory
 > )
 > ------------------------------------------------------------
 > 
 > I don't want to use SAVEDIR; my environment is polluted enough.
 > 
 > But it appears from looking at gnus.el that using SAVEDIR should work
 > (if it's been properly exported), but you're right it doesn't.

I prefer to use SAVEDIR because a number of people here use my setup
stuff, and using env vars lets them put things where they want and not
have to muck around in .emacs, .vm, .gnus, ...

So I use env vars for a bunch of things.  I use the "standard" ones
like SAVEDIR and define new ones like VM_INBOX.  Then in my .vm I
have:

(if (getenv "VM_INBOX")
    (setq vm-primary-inbox (getenv "VM_INBOX")))

Anyway, I have a number of things like this, and it just makes it
easier for other folks to use my stuff.

But back to SAVEDIR.  It looks like the relevant code is right at the
top of gnus.el:

(defvar gnus-directory (or (getenv "SAVEDIR") "~/News/")
  "*Directory variable from which all other Gnus file variables are derived.")

which kinda looks OK, but I'm not an elisp expert at all...

+-----------------------+--------------------------------------------------+
|John A. Turner         |"Music is the cup which holds the wine of silence;|
|Los Alamos Natl. Lab.  |  sound is that cup, but empty;                   |
|e-mail: turner@lanl.gov|    noise is that cup, but broken."               |
|                       |                        - Robert Fripp            |
+-----------------------+--------------------------------------------------+


  reply	other threads:[~1996-06-20 14:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <199606200515.XAA10443@gielgud.lanl.gov.xdiv>
1996-06-20  6:22 ` Mark Borges
1996-06-20 14:18   ` John Turner [this message]
1996-06-20 14:47   ` Lars Magne Ingebrigtsen
1996-06-20 16:56     ` Mark Borges
1996-06-21  6:53       ` 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=199606201418.IAA10828@gielgud.lanl.gov.xdiv \
    --to=turner@xdiv.lanl.gov \
    --cc=ding@ifi.uio.no \
    --cc=turner@lanl.gov \
    --cc=xemacs-beta@xemacs.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).