Henrik Lissner

Results 443 comments of Henrik Lissner

Does this fix the issue for you? ```elisp ;;; add to $DOOMDIR/config.el (defadvice! fixed-+org--optimize-backgrounded-agenda-buffers-a (fn file) :override #'+org--optimize-backgrounded-agenda-buffers-a (if-let (buf (org-find-base-buffer-visiting file)) buf (funcall fn file))) ``` I realize the...

This actually doesn't seem related to `+org--optimize-backgrounded-agenda-buffers-a`, but more on where the cursor is in already-open agenda buffers. I.e. If the cursor is on the second heading, `org-map-entries` only operates...

Oh, this might actually be `sit-for`'s fault. If you swap it out for `sleep-for`, `foo` works in all cases. I suspect it's because it doesn't actually block Emacs, thus allowing...

Are you still seeing this issue? I suspect that https://github.com/doomemacs/doomemacs/commit/ded3f5ec834942044b5caae6ca220270660b466b might've indirectly fixed it; it caused a lot of strange issues to do with buffer focus and lifecycles that *could*...

Does wrapping the body of `foo/minimal-example` in: ```elisp (let (save-place-alist) ...) ``` Fix the issue for you? EDIT: Alternatively: ```lisp (defadvice! +org--inhibit-saveplace-in-agenda-buffers-a (fn &rest args) :around #'org-agenda-prepare-buffers (let (save-place-alist) (apply...

I can't reproduce this on any of my test environments (Arch Linux, Ubuntu, NixOS, MacOS, and Windows; on 28.2, 29.3, 30.0.50, or 31.0.50), so I suspect a local or 29.4...

@dwinkler1: ```sh # EMACSDIR = where you cloned Doom, e.g. ~/.emacs.d or ~/.config/emacs rm -rf $EMACSDIR/.local/straight/build-* rm -rf $EMACSDIR/.local/cache/eln/* doom sync ```

See if recompiling your packages ahead-of-time fixes the issue. I.e. ```sh doom sync --gc --rebuild --aot ``` This will clean up any orphaned build artifacts (and *.eln files), rebuild your...

This should be a considered a bug with whatever you use to launch those compilation buffers. Comint doesn't automatically recognize files, it needs to be told how to by setting...

It's only implemented for vertico because the contributors who PRed them are vertico users and are only aware of the commands that `consult` provides for this functionality. They (and I)...