From: Chris BSomething <xpusostomos@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 37203@debbugs.gnu.org
Subject: bug#37203: 26.2; error on load with .emacs.d symlink on windows
Date: Wed, 28 Aug 2019 16:27:27 +1000 [thread overview]
Message-ID: <CADrHaBF2+KZN_ejU0hOK8MzXb-tFPDuR=rZadpBDxKEbt8LmiQ@mail.gmail.com> (raw)
In-Reply-To: <83r255dd0f.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]
Ahh, ok thanks. Although the link did seem to work for m-x load-file
In any case, i found that mklink /j also seems to work. Some different kind
of link i dont fully understand.
On Wed, 28 Aug. 2019, 4:23 pm Eli Zaretskii, <eliz@gnu.org> wrote:
> > From: Chris BSomething <xpusostomos@gmail.com>
> > Date: Wed, 28 Aug 2019 12:21:50 +1000
> >
> > I want to store my init.el on Google drive so it shares between
> computers.
> > So I created a windows symlink:
> > mklink .emacs.d Google\emacs
>
> This doesn't create a directory symlink, it creates a symlink to a
> (non-existent) file. To make a directory symlink, you need to do this
> instead:
>
> mklink /d .emacs.d Google\emacs
>
> If this doesn't work either, please tell more about what does "Google"
> above represent, as it doesn't seem to point to a drive, at least not
> syntactically.
>
> > It is mistakenly thinking that the directory isn't writable probably
> because it is a <SYMLINK> rather than a
> > <DIR>, or alternatively because the symlink is owned by Administrators.
>
> If ownership winds up to be the problem (I don't think so), it can be
> changed from the Windows Explorer or other similar tools.
>
[-- Attachment #2: Type: text/html, Size: 1699 bytes --]
next prev parent reply other threads:[~2019-08-28 6:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 2:21 bug#37203: 26.2; error on load with .emacs.d symlink on windows Chris BSomething
2019-08-28 6:23 ` Eli Zaretskii
2019-08-28 6:27 ` Chris BSomething [this message]
2019-08-28 6:59 ` Eli Zaretskii
2019-08-28 7:31 ` Chris BSomething
2019-08-28 7:51 ` 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
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='CADrHaBF2+KZN_ejU0hOK8MzXb-tFPDuR=rZadpBDxKEbt8LmiQ@mail.gmail.com' \
--to=xpusostomos@gmail.com \
--cc=37203@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).