You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
starptr
changed the title
default.el behaves subtly different from init.eldefault.el behaves subtly differently from init.elJan 7, 2025
When using
emacsWithPackagesFromUsePackage
, thedefaultInitFile
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 (calleddefault.el
from now) and theinit.el
init file such that expressions that work perfectly fine ininit.el
do not work indefault.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 asinit.el
) would be to wrap the derivation and use the--init-directory
CLI flag to pass in a derivation of theinit.el
file, avoiding usage ofdefault.el
altogether.The text was updated successfully, but these errors were encountered: