Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors persist after fixing what caused them in BBEdit (Texlab 5.13.0) #1042

Closed
ArttuLai opened this issue Mar 14, 2024 · 2 comments · Fixed by #1043
Closed

Errors persist after fixing what caused them in BBEdit (Texlab 5.13.0) #1042

ArttuLai opened this issue Mar 14, 2024 · 2 comments · Fixed by #1043

Comments

@ArttuLai
Copy link

ArttuLai commented Mar 14, 2024

I'm using BBEdit (15.0.1) on macOS Ventura (14.4) as text editor, where I'm compiling .tex files via Tectonic, and using Texlab as language server provider via BBEdit's LSP support. The earlier versions, (like 5.12.4) used to work just fine, but I'm noticing that with 5.13.0, the errors won't go away from BBEdit's UI after I fix them.

E.g. if I type an extra curly brace, there will be a red highlight showing I have error in that line, and there's also another counter that shows the total amount of errors in the active document. But after I remove the brace and fix the error, the error counter still says I have errors, and in general the feature started behaving bit oddly. The .tex file compiles just fine; it just shows the old error, and only way I can get rid of it to relaunch BBEdit.

Going back to 5.12.4 makes it work normally again.

Is there more info I can provide to troubleshoot this further?

Here's a screen recording of the issue.

Edit: here's a second screen recording of Texlab 5.12.4 showing how it's supposed to work.

@samuelqp
Copy link

I am having the same issue using neovim with v5.13.0. Using the command "LspRestart" seems to hide the error message, as well as closing and re-opening the file.

@mathjiajia
Copy link

The same issue,
I have downgraded to 5.12

pfoerster added a commit that referenced this issue Mar 16, 2024
The `MultiMap::retain function` removes the entire entry if the associated `Vec` is empty. Switching to plain `HashMap` fixes the issue.

Fixes #1042.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants