Henrik Lissner

I'll be looking into switching to treesit.el sometime this month (likely to coincide with Doom dropping Emacs 27 support). I'll post here when I start on it/once it's done.

Presumably, you have root access to your android device, so couldn't `/usr/bin/env` be symlinked to wherever Android/Termux's `env` is? Shebang lines are dreadfully inflexible, and I'd rather avoid having to...

> Does that work well? It does not work at all (case in point). I've been meaning to remove it, in fact. It might've worked in the past, but the...

The only thing that comes to mind is the syntax checker, which does not *evaluate* the file, but instead compiles it whenever Emacs is idle (in order to consume the...

Try disabling the `:editor format` module (comment it out in your `doom!` block, run `doom sync` in the shell, then restart Emacs), and see if that changes anything for you.

I think I've finally zeroed in on the cause. It is, in fact, the syntax checker. It loads Doom (and your config) before it compiles an elisp file in your...

Errors about missing `lsp-*` functions usually mean you've forgotten to enable the `:tools lsp` module (or you forgot to run `doom sync` afterwards?). You did not include your `M-x doom/info`...

I can't reproduce Doom *not* picking up the $PATH from its containing environment without: - Running `doom env` from within Emacs (in vterm, eshell, etc), - Making the `emacs` executable...

There *must* be another way. I'm not keen on supporting this degree of symlinkery madness. Calling `file-truename` all over the place is relatively expensive. I opt-out of it *inside* `doom-core-dir`...

Please read the [How to debug](https://doomemacs.org/d/how2debug) guide and investigate the \*Messages\* buffer for errors and warnings. And if you find errors, please produce a backtrace from them (also covered by...