-
Notifications
You must be signed in to change notification settings - Fork 536
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
Autocomplete for '\begin{}' inserts a double closing '}' #2075
Comments
@jlelong actually, I don't, it's auto closing. |
OK I understand. I only type I will investigate if I can remove the extra |
I think this is solved by #2080 |
Preliminary questions [Required]
Disable all the other extensions except for LaTeX Workshop, and check that you still see this issue. [Required]
You still see this issue?: Yes
Make sure to visit the wiki FAQ before filling an issue.
You visited the wiki?: Yes
If your issue is with compiling a document (not having to do with finding the root file of a project), check first that you can compile manually.
You can compile a TeX document manually?: Yes
Describe the bug [Required]
Invalid syntax from autocomplete for \begin{itemize} or \begin{enumerate} causing compilation error.
To Reproduce
When typing:
\begin{i}
The suggestions for autocomplete will appear.
In this case, the relevant suggestion will be:
\begin{itemize}
If I proceed with this suggestion then I will have what follows:
As you can see, the ending command contains an additional closing curly brace.
It's wrong and will cause a compilation error if not removed (manually).
Expected behavior
I want the autocomplite to lead to what's below:
Logs [Required]
Please paste the whole log messages here, not parts of ones. It is very important to identify problems.
LaTeX Workshop Output [Required]
Developer Tools Console [Required]
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop [Required]
Additional questions
Are you using LaTeX Workshop with VS Code Remote?
Yes, I am using LaTeX Workshop
The text was updated successfully, but these errors were encountered: