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

default.el behaves subtly differently from init.el #457

Open
starptr opened this issue Jan 7, 2025 · 0 comments
Open

default.el behaves subtly differently from init.el #457

starptr opened this issue Jan 7, 2025 · 0 comments

Comments

@starptr
Copy link

starptr commented Jan 7, 2025

When using emacsWithPackagesFromUsePackage, the defaultInitFile option cannot be used as a drop-in replacement for ~/.emacs.d/init.el. There are strange differences in behavior between the default init file (called default.el from now) and the init.el init file such that expressions that work perfectly fine in init.el do not work in default.el. (See noctuid/general.el#549 for just one example. As another example, :bind in a use-package expression does not work in some situations, but I haven't had a chance to triage this issue yet.)

Perhaps this fact is actually obvious to experienced users of emacs. I am not an experienced user, but it would be nice for this to be at least documented somewhere. An even better fix ("hotfix" might be a better word here if this is actually an upstream bug in emacs itself and default.el is supposed to behave exactly the same as init.el) would be to wrap the derivation and use the --init-directory CLI flag to pass in a derivation of the init.el file, avoiding usage of default.el altogether.

@starptr starptr changed the title default.el behaves subtly different from init.el default.el behaves subtly differently from init.el Jan 7, 2025
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

1 participant