From: "François Pinard" <pinard@iro.umontreal.ca>
Cc: ding@gnus.org
Subject: Re: unwanted News and News/drafts directories
Date: 23 Sep 1998 08:56:40 -400 [thread overview]
Message-ID: <oq90jbkmwn.fsf@icule.progiciels-bpi.ca> (raw)
In-Reply-To: Justin Sheehy's message of "22 Sep 1998 14:25:06 -400"
Justin Sheehy <justin@linus.mitre.org> écrit:
> François Pinard <pinard@iro.umontreal.ca> writes:
> > Justin Sheehy <justin@linus.mitre.org> writes:
> > > John H Palmieri <John.H.Palmieri.2@nd.edu> writes:
> > > > (setq gnus-directory (expand-file-name "~/Mail/News")
> > > Move that from ~/.gnus to ~/.emacs, so that those variables are set
> > > when Gnus starts.
> > Is that move really needed? I preset all directory variables for Gnus in my
> > `.gnus' file instead of `.emacs'; it seems to work as expected for me.
> Several variables inherit from gnus-directory at startup time. If that
> variable is not already set, then the others will inherit the wrong value.
> Yes, the move is necessary.
For a long while, I used in `.gnus' (not in `.emacs') the following:
(setq gnus-default-directory (expand-file-name "~/")
gnus-kill-files-directory "~/.scores"
nndraft-directory "~/.nndraft/drafts/"
nnml-directory "~/.nnmail/"
gnus-soup-directory "~/.soup-brew/"
nnsoup-directory "~/.soup/"
gnus-article-save-directory "~/")
[The above is extracted from something bigger, I hope I did not forget any.]
> It is certainly possible that one could carefully arrange things to be set
> in ~/.gnus and have them work correctly, but there is a strong posibility
> that one would forget to set at least one of the directory variables.
One thing I see is that I use `gnus-default-directory', and that I did not
touch `gnus-directory', which still has "~/News/" as a value, here. I do
not even have an existing "~/News" directory! Looking at both docstrings,
they seem unrelated. Also, the documentation of `gnus-directory' does
explicitly suggest that it be initialised from `.emacs', not `.gnus'.
The first time I played with these variables, years ago, it did not work
as I expected. I reported a bug, Lars corrected something, and it works
since then.
--
François Pinard mailto:pinard@iro.umontreal.ca
Join the free Translation Project! http://www.iro.umontreal.ca/~pinard
prev parent reply other threads:[~1998-09-23 12:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-16 19:20 John H Palmieri
1998-09-19 12:23 ` Lars Magne Ingebrigtsen
1998-09-22 15:44 ` Justin Sheehy
1998-09-22 17:29 ` François Pinard
1998-09-22 18:25 ` Justin Sheehy
1998-09-23 12:56 ` François Pinard [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=oq90jbkmwn.fsf@icule.progiciels-bpi.ca \
--to=pinard@iro.umontreal.ca \
--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).