What happened?
So much. I am completely new to all of this, so forgive my ignorance. I tried following the install guide on the github. I had already been playing around with emacs, so I uninstalled it and deleted ~/.emacs.d/ to get rid of any old configurations. After my initial install, I open emacs, and it gives me the error while loading early-init.el file and told me to run doom sync.
An odd issue I ran into here- when I try to run doom <command>, I get told permission-denied ("Creating directory" "Permission denied".... When I try to sudo the command, I get told sudo: doom: command not found. I have added it to my $PATH via export PATH="$HOME/.emacs.d/bin:$PATH. My PATH now looks like this:
/home/<username>/.emacs.d/bin /home/<username>/.cargo/bin /usr/local/bin /usr/bin /bin /usr/local/sbin /usr/sbin /sbin
so it is in there. I found that being in the ~/.emacs.d/bin directory and running the command as sudo ./doom <command> works.
Anyway, I ran doom sync (via the method described above) and everything seemed to go well, so I reopened emacs, but with the same error. I run doom doctor, and it tells me that the version of emacs I have (29.4) could cause unexpected issues,that Doom is installed in a non standard location, and that it found another emacs config. I actually upgraded my computer from Fedora 41 to 42 because I saw that a newer emacs (30.1) was in the 42 repositories. I don’t understand these other two issues, because as far as I can tell, they’re not true. I only have one ~/.emacs.d location, and it was created when I ran the git clone command for the Doom install. I don’t have a .config/emacs location, the only place I can seem to find any configs for emacs is in this one directory, which was created at the beginning of the Doom install process.
I’ve tried uninstalling and reinstalling both emacs and Doom a couple of times, trying to completely erase all prior existence to give it as clean a slate as possible, with no luck.
I also ran emacs --debug-init, and it told me: Debugger entered--Lisp error: (doom-nosync-error ..... I tried searching for that, and fell upon this github issue where they talked about blowing away the .local file, so I tried that as well, running doom sync afterward with no success. I have included the full dump of both doom doctor and emacs --debug-init below.
What did you expect to happen?
Doom emacs should’ve loaded and opened.
Steps to reproduce
- …
- …
- …
System information
doom info dump:
Loading data dump...
doom doctor dump:
Loading data dump...
emacs --debug-init dump:
Loading data dump...