From: Evan Driscoll <driscoll@cs.wisc.edu>
To: Barry OReilly <gundaetiapo@gmail.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: How to specify path to .emacs.d
Date: Tue, 30 Oct 2012 11:09:24 -0500 [thread overview]
Message-ID: <508FFBB4.9080105@cs.wisc.edu> (raw)
In-Reply-To: <CAFM41H3JAPpDLHB279MPgonLWf1EE-WzGuSFmPYR7eszfYVGvA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1540 bytes --]
On 10/29/2012 03:37 PM, Barry OReilly wrote:
> Another use case is that I'm getting my Emacs configuration to work on
> Windows, and I discovered that Windows shortcuts are apparently .lnk
> files and don't function like a symlink. I'm unsure how to use a
> .emacs.d at an arbitrary location, and only know to copy it to home
> instead. This is inconvenient because I want to use a .emacs.d straight
> out of a Mercurial repo located elsewhere.
I can't help with the Emacs part of your question, but Vista and higher
have true (though still a bit brain dead in some respects) symlinks.
Look at the 'mklink' command.
You'll need a privilege that isn't granted to users by default (silly
decision #1), and while you can change that, for a one-off thing it's
easier to just elevate yourself when opening the command prompt. Also
note that Windows symlinks are specific to either pointing to a file or
a directory, so you'll have to explicitly tell 'mklink' that you want a
directory symlink.
On XP and 2000 (and also Vista and higher) you also have both hard links
and something called "directory junctions" available. (Windows is
capable of creating hard links to directories. Presumably you have to be
careful not to shoot yourself in the foot by creating a cycle.) I think
'mklink' may create hard links too though I'm not sure; for directory
junctions, there are a couple third-party utilities, e.g. Mark
Russinovich's 'junction':
http://technet.microsoft.com/en-us/sysinternals/bb896768.aspx
Evan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 554 bytes --]
next prev parent reply other threads:[~2012-10-30 16:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 20:37 How to specify path to .emacs.d Barry OReilly
2012-10-29 22:27 ` Peter Dyballa
2012-10-30 9:46 ` Nicolas Richard
2012-10-30 13:30 ` Peter Münster
2012-10-30 14:44 ` Jambunathan K
2012-10-30 16:09 ` Evan Driscoll [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-30 22:53 Barry OReilly
2012-10-31 10:26 ` Nicolas Richard
[not found] <mailman.12027.1351637586.855.help-gnu-emacs@gnu.org>
2012-10-31 0:51 ` Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=508FFBB4.9080105@cs.wisc.edu \
--to=driscoll@cs.wisc.edu \
--cc=gundaetiapo@gmail.com \
--cc=help-gnu-emacs@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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).