Jostein Kjønigsen
Jostein Kjønigsen
Not that I know. Whoever wants it, will have to send in a patch :)
@marijnh: It seems like you're the ones who are best suited to deliver this. I think the best option is you package this as a PR. To me it sounds...
I think a better plan than creating framework-specific completion-mechanisms would be to create an implementation that just works with `completion-at-point`. Basically what [this issue](https://github.com/ananthakumaran/tide/issues/62) asks for. That would solve it...
I concur. Not sure it's an exact duplicate, but this seems somewhat related to https://github.com/ananthakumaran/tide/issues/61.
PRs welcome.
I'm not going to make any statements on @AdamNiederer's behalf, but I would suspect that supporting a language server is something you request in [lsp-mode](https://github.com/emacs-lsp/lsp-mode), a minor-mode and LSP-client dedicated...
This PR now has some slight conflicts with git master. Can you resolve those? 🙂
First of all: This is Emacs using Git master, right? Second: I'm not sure this *can* be fixed while maintaining full compatibility with all supported versions of Emacs. So... Are...
Feel free to try out the proposed changes in the PR. If it breaks compatibility, I'm sure the CI will let us know :)
> font-lock-fontify-buffer is already avoided on versions of Emacs that provide font-lock-ensure, as the code surrounding the warning's location show Yeah. This was the reason why I asked about actual...