Henrik Lissner

I see you have an envvar file loaded. Have you regenerated it lately? I.e. `doom env` (in a native terminal, not vterm, eshell, or any other terminal emulator _in_ Emacs)...

> Running M-x doom/reload-env doesn't help at all. @y-mx-b This only re-reads your envvar file, it doesn't regenerate it. To quote `doom/reload-env`'s docs: > Reloads your envvar file. > >...

Very odd. If your `PATH` is correct, then `M-x eval-expression RET (executable-find "fd")` (on Ubuntu and some other distros, it's `fd-find`, not `fd`) should return the correct path to `fd`....

I'm aware of this, and the format module is pending a rewrite to replace format-all with [apheleia](https://github.com/raxod502/apheleia). Bumping format-all is in [our do-not-PR list](https://discourse.doomemacs.org/do-not-pr) because it has introduced breaking changes...

This occurs because I've recently changed the value of `user-init-file` to point to `doom-start`, which is not the correct entry point for bootstrapping Doom anymore. To help me confirm that...

@VitalyAnkh I've changed the snippet above. See if replacing the advice fixes your issue.

As of 551f0ca this should be resolved. Let me know if that isn't the case and I'll reopen it.

The cause seems to be that bin/doom.cmd is outdated (and updating it will require more than simply correcting the `..\init.el` filepath, see #6615). Unfortunately, I don't know Windows batch scripting...

I agree. I will think about it after I'm finished with the documentation update.

Sorry for the late response. I've converted this to a draft because I agree the issue should be addressed, but a better solution is needed, as this issue will affect...