opened 11:13AM - 07 Dec 19 UTC
closed 12:36PM - 15 Dec 20 UTC
bug
emacs-bug
Steps to reproduce:
1. Open a well formatted C++ file, where eglot shows no e…rrors and warnings.
2. Add 2 lines of comments, for example
```
// comment1
// comment2
class MyClass {
...
more code
...
```
3. Put cursor in the comments, and press `M-q` (c-fill-paragraph)
4. Observe flymake now shows some errors even though there is no change in actual code
5. Keep pressing `M-q` and we can observe the error lines move down
It feels as if eglot didn't realize the input command happens in comment and doesn't affect code at all. Instead, eglot seems to send comments as code for incremental parsing and generated errors.
The errors can be fixed by reverting the buffer.