Henrik Lissner

As of c27621a this should be resolved locally, at least until emacs-evil/evil#1971 is addressed. Thanks for bringing it to my attention!

I'm not sure what to make of this, since I cannot reproduce it. The one difference between our setups is `org-roam-ui`. Could you try disabling it and see if that...

This seems more like an OS/DM level issue than an Emacs one. See if this helps: ```elisp ;;; add to $DOOMDIR/config.el (add-to-list 'default-frame-alist '(inhibit-double-buffering . t)) ``` If not, try...

emacs-pgtk should work on X11 too. Another possibility is a compositor. Do you use something like picom? If so, try disabling it.

Hmm. I haven't been able to reproduce it so far. Here are some more things to try: 1. Increase `dirvish-input-debounce`: ```elisp ;;; add to $DOOMDIR/config.el (after! dirvish (setq dirvish-input-debounce 0.1))...

> running vanilla emacs 30.1, dirvish 20250415.706 from melpa. This appears to be an upstream issue. Please report it to https://github.com/alexluigit/dirvish/issues as well. > ran profiler for a few seconds,...

I can't reproduce this. Some things to try: - Interrupt Emacs itself by executing `pkill -USR2 emacs` in the terminal. This should (hopefully) force Emacs to stop what it's doing...

> I used command pkill -USR2 /opt/homebrew/Cellar/emacs-plus@30/30.1/Emacs.app/Contents/MacOS/Emacs, but it didn't work. You need to do `pkill -f ...` if you use the whole full process path. Does `pgrep -f /opt/homebrew/Cellar/emacs-plus@30/30.1/Emacs.app/Contents/MacOS/Emacs`...

Do either of these snippets fix the issue for you? ```elisp ;;; add to $DOOMDIR/config.el (after! compile (remove-hook 'compilation-filter-hook #'ansi-color-compilation-filter)) ``` ```elisp ;;; add to $DOOMDIR/config.el (after! compile (remove-hook 'compilation-filter-hook...

It seems like the python process is endlessly spamming comint with newlines and `1`'s. Not quite sure what that's about.