Henrik Lissner

I am aware of this issue, but is currently low priority (and _may_ be addressed as part of #4273). I'll welcome a PR to fix it ahead of me.

Does this conflict at all with #6568?

This seems like an upstream issue. Does unpinning `org` fix it? 1. Add `(unpin! org)` to `$DOOMDIR/packages.el` (e.g. `~/.doom.d/packages.el`). 2. Run `doom sync -u`. 3. Restart Doom.

You need to defer it, to have it prepend to its default value (applied when the mode is loaded). ```lisp (after! rustic (set-company-backend! 'rustic-mode ...)) ```

To follow up on #5674, `set-company-backend!` itself is deterministic. It prepends its arguments to `company-backends` _in load order_. Typically, that means 1. minor-mode-specific, 2. major-mode specific, then 3. global defaults,...

It should be possible to do so, but I'm already working on a rewrite for the format module (powered by apheleia). I've pushed it to [my private config](https://github.com/hlissner/doom-emacs-private/tree/master/modules/editor/format) if you'd...

I'm not currently accepting new editing paradigm modules in Doom so I must turn this down, but I will be opening up a repository for community-developed modules in https://github.com/doomemacs/contrib-modules (not...

@bsag Could you tell me if the `+python-current-version` variable contains the correct version?

I've pushed a potential fix for this. So long as pyenv's shims directory is in your `PATH` (and `exec-path`, by extension), `+python-current-version` should contain the current version. Please update and...

@bsag Have you been using Emacs through the daemon all this time? That would explain a lot, because Doom uses `exec-path-from-shell`, but only in GUI sessions (not daemon or terminal...