From: SDS <sds.biz.main@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 16087@debbugs.gnu.org
Subject: bug#16087: Setting HOME environment variable in Emacs on Windows has side effects
Date: Sun, 08 Dec 2013 16:14:11 -0500 [thread overview]
Message-ID: <52A4E123.1080107@gmail.com> (raw)
In-Reply-To: <83lhzvyuj4.fsf@gnu.org>
On 12/8/2013 3:09 PM, Eli Zaretskii wrote:
> Thanks. So this sounds like a one-time issue, which, once solved to
> your satisfaction, should never pop up again, right?
A workaround which directly or indirectly prevents this from happening
is fine. It hasn't even really been an issue unless I'm trying to access
files within the directory containing the .emacs.d for NT-Emacs. I
noticed it when I tried to open .emacs.d/init.el for NT-Emacs and it
opened the init.el for Emacs-w32 instead.
I could isolate the .emacs.d for NT-Emacs inside its own directory, and
point to that in HKCU\SOFTWARE\GNU\Emacs\HOME before changing HOME in
init.el. That way it's only a problem when trying to edit the init.el
for NT-Emacs, which I could workaround by invoking NT-Emacs with --no-init.
I just wasn't sure if there were any other apparent side effects to
changing the HOME directory in the init.el file. I figured out already
that doing so requires changing HOME at the end of init.el, and setting
some directory variables to the full path pointing to .emacs.d for
NT-Emacs. I also wasn't sure if a better/simpler workaround existed.
> As for setting this up, my suggestion would be to set HOME in the
> environment to point to the Cygwin's HOME, and augment that by
> whatever you need in the Bash init files.
Won't that require merging the .emacs.d directories for the two ports?
Is there a way of doing this without having them interfere with each other?
Cheers,
SDS
next prev parent reply other threads:[~2013-12-08 21:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-07 20:45 bug#16087: Setting HOME environment variable in Emacs on Windows has side effects SDS
2013-12-08 17:38 ` Eli Zaretskii
2013-12-08 19:44 ` bug#16087: " SDS
2013-12-08 20:09 ` Eli Zaretskii
2013-12-08 21:14 ` SDS [this message]
2013-12-09 3:43 ` Eli Zaretskii
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=52A4E123.1080107@gmail.com \
--to=sds.biz.main@gmail.com \
--cc=16087@debbugs.gnu.org \
--cc=eliz@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.