Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Symlinked init file #44

Open
sho-87 opened this issue May 16, 2017 · 2 comments
Open

Symlinked init file #44

sho-87 opened this issue May 16, 2017 · 2 comments

Comments

@sho-87
Copy link

sho-87 commented May 16, 2017

My emacs dir is c:\Users\Simon\.emacs.d

Inside is my .init.el file, however, it is symlinked to the actual file which is stored in my dropbox directory: d:\dropbox\emacs\.init.el

When I run esup I expect it to use my .emacs.d directory, and not my dropbox directory. However, when esup starts it is downloading all of the packages again to my dropbox dir, and I think its due to the symlink

The location of my user init file is correct (Simon\.emacs.d).

Is there any way to get esup to use the .emacs.d directory without following the symlink and downloading everything again to the dropbox dir?

My config is here if it helps

@jschaf
Copy link
Owner

jschaf commented Jul 26, 2017

Try this, you can pass in a file manually to have Emacs profile it.

(esup "c:/Users/Simon/.emacs.d/init.el")

By default, esup uses user-init-file. Emacs probably resolves the symlink to the dropbox folder on startup, so esup only ever sees the resolved file.

@raxod502
Copy link
Contributor

This is rather interesting since I also have an init.el file symlinked in from somewhere else, and have never experienced this sort of problem with esup. I bet it's a Windows-only issue (I use macOS) since symlinks are handled differently on Windows.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants