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
All I did was run this command on macOS ventura \w Macbook Pro M1
nix run github:nix-community/nix-doom-emacs
the command has zero STDOUT and STDERR, successfully launched emacs, but emacs appeared 'stock', and has these errors
Warning (initialization): An error occurred while loading ‘/nix/store/gq5zh1fzib4kvfil8rk8a4x39r0lyfq7-emacs-28.2/lib/emacs/28.2/native-lisp/28.2-d7595b2e/warnings-28e75f4d-870b026e.eln’:
Doom hasn't been initialized yet; did you remember to run 'doom sync' in the shell?: /nix/store/vvcvdipbss5zqisbmahr2znbvwqbfhd7-straight-emacs-env/etc/@/init.28.elc
To ensure normal operation, you should investigate and remove the
cause of the error in your initialization file. Start Emacs with
the ‘--debug-init’ option to view a complete error backtrace. Disable showing Disable logging
The text was updated successfully, but these errors were encountered:
jasonjckn
changed the title
Bug: "Doom hasn't been initialized yet; did you remember to run 'doom sync' in the shell"
Bug: "Doom hasn't been initialized yet"
Feb 24, 2023
/nix/store/…-straight-emacs-env/etc/@/init.28.elc feels pretty remarkable, maybe @thiagokokada but generally we are not very equipped for the surprisingly high constant maintenance load that comes with following Doom upstream — we're still stuck on an old version: #316. #353 details how to fix this but no one has successfully put in the investment yet. (I did try, a while ago, with less knowledge about Emacs and related things; ended up with frustration and big piles of half-working unmaintainable Elisp and very long weird shell invocations…)
All I did was run this command on macOS ventura \w Macbook Pro M1
the command has zero STDOUT and STDERR, successfully launched emacs, but emacs appeared 'stock', and has these errors
The text was updated successfully, but these errors were encountered: