Colin Woodbury
Colin Woodbury
Especially hiding kernel threads and highlighting base names.
> Is parinfer a LSP client? It's not, but it does watch the buffer and make automatic corrections based on where parens go. I should have mentioned that I'm using...
Ah let me clarify. I am using `racket-mode`, which is a "major mode", but Emacs also has "minor modes" which run alongside the majors. `parinfer` is such a minor mode....
A comment from the Doom Emacs maintainer: > Just a hunch, but it sounds like parinfer is modifying the buffer without triggering the modification hooks lsp-mode uses to report buffer...
Yes. The full answer is that I'm using the `racket` module in [Doom Emacs](https://github.com/hlissner/doom-emacs), which includes `lsp-mode`. It's this `lsp-mode` that hooks into `racket-langserver` when in an `.rkt` buffer.
A similar issue exists for `PropertyT`.
Any more thoughts here? Or should we just consider it incorrect to pattern match in this way in tests?
Any updates on this?
`makepkg` already supports having a `install.sh` file separate from the PKGBUILD. Would that suffice?