Closed 13hannes11 closed 2 years ago
I had the same problem. I solved it by removing the following setting from devcontainer.json
"latex-workshop.viewer.pdf.internal.port": 35555,
However, this setting isn't a default one (I recommended adding it in https://github.com/James-Yu/LaTeX-Workshop/issues/2206#issuecomment-674092455), so maybe you are having a different issue.
@CheariX mine is set to the default (0) so this doesn't seem to be the issue but it might be that vscode cannot properly communicate with the pdf viewer.
Due to me being on Fedora Silverblue I am running VSCode as flatpak. Maybe that's part of the issue.
Preliminary questions [Required]
Disable all the other extensions except for LaTeX Workshop, restart VS Code, and check that you still see this issue.
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]
When being connected to a container (in my case podman container from toolbox in fedora silverblue) the pdf viewer does not update after a compilation is done via file watching. Closing the viewer and reopening it shows the changes.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
After compilation inside a container the PDF viewer should automatically refresh the view to show the updated document.
Logs [Required]
LaTeX Workshop Output [Required]
Developer Tools Console [Required]
Nothing suspicious.
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?
Yes
Are you using LaTeX Workshop with VS Code Remote?
Yes
If the answer is Yes, please write which one you are using. Write the versions of the remote extension.