"View documentation" link on \usepackage{...} hover doesn't work with Snap version of VSCode #2437
Labels
external issue
Issue with something else than LaTeX-Wokshop
Comments
|
I cannot reproduce either. @FMuro The logs say |
From command line it works like a charm. It just opens the PDF. I have vscode installed as a snap. I don't know if this makes any difference because it's a classic one, though. |
|
|
|
Does it work when you run the |
It does.
This doesn't work from the recipe (although it does from terminal). From the recipe, I get: |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
is probably the result of an error in the recipe definition. Can you try "latex-workshop.latex.recipes": [
{
"name": "xdg",
"tools": [
"xdg"
]
}
],
"latex-workshop.latex.tools": [
{
"name": "xdg",
"command": "xdg-open",
"args": [
"/usr/share/texlive/texmf-dist/doc/latex/amsmath/amsldoc.pdf"
],
"env": {}
}
] |
|
Thanks for elaborating. Here you have what I get: |
|
Great. Does the |
Unfortunately not. I hoped you'd find some clue here, maybe the "No PDF viewer connected...", although the file referred to therein is not the doc file. |
|
So, we have narrowed down the original issue -- texdoc not opening any documentation -- to the inability of The |
|
When you run the |
|
I did not pay much attention when you mentioned |
This doesn't work either. So strange... It fails exactly in the same way as the default command. It reports to be opening it but nothing shows up. No errors in the |
Which underscore are you talking about? Which viewer did you try for My feeling is that all this is related to |
I tried with and without, both.
Sure, I'll do this this afternoon. |
|
Searching "ubuntu snap open pdf" on Google, you will find a lot of posts on issues opening pdf files from snap applications. I am afraid we cannot do much on our side, so I am closing the issue. If you come up with solution, please let us know. |
|
I've tried with the |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
No, wait a minute. I was trying to run the downloaded binary from the command line in the usual way, but somehow it was another copy of the snap what was launched. Just checked the processes. Closing the snap and running the binary, everything works. Sorry for the confusion. Keep this closed, I'll report to the snap people. |
|
I am so happy, we have finally found the issue! |
|
Yeah, it might be the same as this one, where I've posted a link to this report: https://forum.snapcraft.io/t/xdg-open-not-working-on-firefox/17670/16 |
Repository owner
locked as resolved and limited conversation to collaborators
Jan 4, 2021
jlelong
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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,
texdocis inpath. I've tried with the full path and it doesn't work either. BTW,texdocworks without issues from terminal.Describe the bug [Required]
Hover a \usepackage{...} and click on "view documentation", or run "LaTex Workshop: Show package documentation" or "LaTex Workshop: Show package documentation actually used". None of them works,
To Reproduce
Steps to reproduce the behavior:
Or:
Or:
Expected behavior
A PDF with the docs should open. I've tested with packages which all have docs, and running
texdocfrom CLI works as expected. The similar functionality in Emacs also works.Logs [Required]
Please paste the whole log messages here, not parts of ones. The log should start with
Initializing LaTeX Workshop. 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 VSCodium?
No
Are you using LaTeX Workshop with VS Code Remote?
No
The text was updated successfully, but these errors were encountered: