Mekeor Melire

Here's a quote from the [Org info manual](https://www.gnu.org/software/emacs/manual/html_node/org/Comment-Lines.html): > Finally, a ‘COMMENT’ keyword at the beginning of an entry, but after any other keyword or priority cookie, comments out the...

I just tried out removing the `COMMENT` keyword: https://github.com/mekeor/taxy.el/tree/4633fa9c0e1bf97678d0cf032924599d04a8c9bb Unfortunately, when the `COMMENT` keyword is removed, GitHub will render these sections into HTML. This is really a bug in GitHub...

Thanks for your report. I was also about to report it right now. :D Flymake indeed [uses](https://git.savannah.gnu.org/cgit/emacs.git/tree/lisp/progmodes/flymake.el?h=44fcab04f6a346e602f00a6d9f5b0e6f0dbeb5e0#n752) the `before-string` text-property. @minad, should I report a bug to flymake/emacs, wishing it...

After replacing `before-string` with `after-string` in the referenced code of line, then reevaluating[^1] that defun, fixes the issue for me. [^1]: Use `eval-defun` (C-M-x) rather than `eval-last-sexp` (C-x C-e) since...

@minad, replacing before-string with after-string in flymake's code leads to another problem: when the flymake-error ranges until the end of a line, then the diagnostics is shown on the next...

> this was specifically due to the semantic tokens feature of LSP I suggest to close this issue as a consequence of this fact.

I see, alright. I was able to reproduce it and see the problem. I wonder how to find out whether the language server needs too long for this, or if...

I enabled LSP logging with `M-: (setopt lsp-log-io t)` and opened the logs in a lean4-mode-managed buffer with `M-x lsp-switch-to-io-log-buffer`. Then I inserted `def a : Nat := a` into...

I forked [bustercopley/lean4-mode](https://github.com/bustercopley/lean4-mode), called it *Nael* and made it more minimalist by sticking to Emacs' built-in facilities like Eglot but also ElDoc and Project. (Nael is currently available at [codeberg.org/mekeor/nael](https://codeberg.org/mekeor/nael)...

I'd also guess that this is due to [`lsp-ui-sideline`](https://emacs-lsp.github.io/lsp-ui/#lsp-ui-sideline). There are some related issues reported there: - https://github.com/emacs-lsp/lsp-ui/issues/661 - https://github.com/emacs-lsp/lsp-ui/issues/746 I'd suggest to close this issue.