-
Notifications
You must be signed in to change notification settings - Fork 535
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
command 'latex-workshop.onEnterKey' not found #2845
Comments
I have the same issue. When reverting to version 8.19.2, the issue disappear. https://github.com/James-Yu/LaTeX-Workshop/wiki/FAQ#install-an-older-version-of-latex-workshop Version : 1.59.1 (VSCodium) |
Same here : using codium, under ubuntu. |
@8hur can you please post some more info about your setup? I was worried that it's related to my remote setup (gitpod.io has previously been frowned upon by the latex-workshop maintainers, #2772 ). |
Please report to https://github.com/open-vsx/publish-extensions/issues The We don't support GitPod and VSCodium. We recommend you to use VS Code. |
Preliminary questions [Required]
Disable all the other extensions except for LaTeX Workshop, restart VS Code, 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?: Not applicable
Describe the bug [Required]
Pressing enter inside the editor for a .tex file does not create a new line but rather shows the warning
command 'latex-workshop.onEnterKey' not found
in the bottom right corner.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Enter key works as it should when typing normally
Logs [Required]
The TeX pane on the left is not visible, even when a .tex file is opened.
LaTeX Workshop Output [Required]
The TeX pane on the left is not visible, even when a .tex file is opened.
Developer Tools Console [Required]
The only extension-related log message I see is:
However, that might be related to me reinstalling the extension a couple of times.
Screenshots
Just to add some color to this issue, here's the little warning window :)
Desktop [Required]
Please write exact version numbers. Please don't write
latest
instead of exact numbers.Additional questions
Are you using VSCodium?
No
Are you using the Snap or Flatpack versions of VS Code?
No
Are you using LaTeX Workshop with VS Code Remote?
Not really - I don't have a local and remote vscode installation, it's kind of remote-only (vscode in browser)
Additional context
Since I can't see the TeX menu at all, this might be related to some other issues more important than pressing enter. Note that #961 / #903 are unrelated as I've disabled all other extensions. Also, #1193 and #2463 show the same error message but aren't a duplicate since they were windows-related.
This only started happening today, version 8.20.2 was released only a couple of hours ago to openvsx, so I suspect that broke something. Unfortunately, I can't find 8.20.1 anywhere and don't know which version I was using previously. I can say that the issue does not exist in 8.19.2.
I find it slightly strange that this release came much later than the git corresponding git tag, not sure if that's normal (I can't see any auto-release workflows, so it might be expected).
Another weird thing: I've compiled the extension myself (current master aswell as 8.20.2 tag) and the issue doesn't exist with either of those versions. I think something may be wrong with the openvsx release.
Lastly, I think the keyboard debug output would be helpful:
For now, I can just disable
config.latex-workshop.bind.enter.key
or delete the shortcut entirely to get enter working again. However, that's more of a workaround than a fix.(I don't use the TeX menu at all, so the fact that that's missing isn't a problem for me. I merely use LaTeX workshop for its syntax highlighting and pdf viewer)
The text was updated successfully, but these errors were encountered: