Stéphane Marks
Stéphane Marks
At the very least, could add the build artifact that shows the homebrew versions of the downloaded dependencies. When weird things arise, it'll be a reference that saves us all...
Indeed, nix > homebrew. I greatly dislike homebrew's total lack of reproducibility across systems and across time and coupled with homebrew's very early deprecation of platform support (Monterey not supported...
> It would generally be a good idea to do a resource lock, but I have several problems with this particular implementation. > > * By default, locking is useless...
FYI, just this morning, I was experiencing an almost identical issue, though on a python buffer and repeatable in fresh Emacs sessions. My indent-bars config uses :demand t and :init...
On Emacs 29.3, I'm getting tons of ```jit-lock-function``` errors in plain ```elisp-mode``` editing init.el (hacking this is a story that has no end)... ```prism-mode``` also slowing down editing pretty substantially....
Seems solved via latest ELPA (I checked it's identical to master). Thank you for following up on this.
Yeah yeah I'll have to write (rx (zero-or-more anything) "ELPA") from now on :)
For the time being, I'm using this hack: ```elisp (defun my/markdown-enter-key-advice (orig-fun &rest args) (let* ((bounds (markdown-get-enclosing-fenced-block-construct)) (markdown-indent-on-enter (if bounds t markdown-indent-on-enter))) (apply orig-fun args))) (advice-add 'markdown-enter-key :around #'my/markdown-enter-key-advice) ```
Do the maintainers agree this is a bug? Should I prepare a PR?