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

lein.sh should not hardcode ~/.emacs.d #3572

Closed
slotThe opened this issue Nov 5, 2023 · 3 comments
Closed

lein.sh should not hardcode ~/.emacs.d #3572

slotThe opened this issue Nov 5, 2023 · 3 comments
Assignees

Comments

@slotThe
Copy link

slotThe commented Nov 5, 2023

Currently, lein.sh hardcodes ~/.emacs.d in case any errors are reported by lein and puts an error file there. This seems like the wrong thing to do, as the user's config itself does not need to reside there. Judging from the mkdir -p ~/.emacs.d, that much is known. It can, however, result in extremely surprising behaviour, as Emacs still prefers those paths. By this I mean that even though one might use XDG-like conventions, the mere existence of a ~/.emacs.d directory will push Emacs towards using that as the place for the config—once hit by a lein error, the user will be greeting by a completely vanilla instance upon restart!

I guess one could do emacs --batch --eval "(princ user-emacs-directory)". I'm not sure how hacky this is (well, really I know :); either way, there is probably at least one good way to get the correct directory.

@vemv vemv self-assigned this Nov 5, 2023
@vemv
Copy link
Member

vemv commented Nov 5, 2023

Thanks for a sensible issue report!

We already honor XDG JVM side so it would be no issue to also do it Elisp side.

This should be improved early in the week.

Cheers - V

@vemv vemv closed this as completed in 1c1ef92 Nov 6, 2023
@slotThe
Copy link
Author

slotThe commented Nov 6, 2023

Well that was fast; thank you so much!

@vemv
Copy link
Member

vemv commented Nov 6, 2023

🍻!

Happy to have users opting in to enrich-classpath - other feedback welcome anytime.

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

2 participants