From: Shanks N <shanks.n@gmail.com>
To: ding@gnus.org
Subject: Emacs 22.1 windows port, gnus and $HOME issues
Date: Mon, 04 Jun 2007 22:37:07 +0530 [thread overview]
Message-ID: <ufy57wsw4.fsf@gmail.com> (raw)
On windows, the latest Emacs release seems to use
c:/Documents and settings/<user>/Application Data/ as the home path.
Fair enough, as it keeps users on 1 machine from trampling on each
other.
But this seems to mess with gnus in that I don't know all the
variables which need to be changed to point to the existing setup.
I have 0.6 in c:/gnu/elisp/nognus.6/, my Mail and News in c:/Mail and
c:/News.
All the other files are currently under c:/ i.e.
c:/.gnus.el
c:/.newsrc.eld
etc.
I'm the only user of the system. I thought making a simple
redirection for _emacs and .gnus.el would solve the problem.
It did partly.
one line (load-file "c:/_Emacs") as the _emacs file in the user/app
data seemed to sort out the Emacs init file issues at least.
What should I do for Gnus?
In Emacs 22, it creates the Mail, News and eld file under user app
folder while I want it to use the existing one under c:/
regards,
Shanks
--
next reply other threads:[~2007-06-04 17:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 17:07 Shanks N [this message]
2007-06-04 20:50 ` Reiner Steib
2007-06-05 15:14 ` Shanks N
2007-06-05 16:37 ` Reiner Steib
2007-06-06 14:53 ` Shanks N
2007-06-11 16:12 ` Shanks N
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=ufy57wsw4.fsf@gmail.com \
--to=shanks.n@gmail.com \
--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).