Replies: 4 comments
-
The same issues exist with Skim, so that gives me to believe this is entirely related to keybindings and how latex-workshop is translating them internally. Inverse-search works fine with both Sioyek and Skim, so I guess Synctex is actually working properly. I am wondering if this is just a matter of how the keybindings are translated into the executable commands, or if it is something way simpler than that. |
Beta Was this translation helpful? Give feedback.
-
As external viewer is not a formally supported feature, I’m converting this issue to a discussion thread. Users may go on discussing over there. |
Beta Was this translation helpful? Give feedback.
-
It appears as if VSCode is actually receiving the correct keybindings. See keybinding debug traces below:
How do I figure out why it is not sending out the requisite command based on the command specified in the file? |
Beta Was this translation helpful? Give feedback.
-
Don't waste any more time—after trying at least 10 different solutions, the only one that works is installing the Full MacTeX |
Beta Was this translation helpful? Give feedback.
-
It appears that forward search does not work (or something seems to be broken) with Sioyek on macOS Ventura 13.2.1. Everything is at the latest build. I know this is not a supported configuration, but I am trying to figure it out since it is on the Wiki. I have exhausted my searching options (including whatever stuff ChatGPT and Bing chat have to throw at me (kudos, since they found some links even I could not find) and resorting to opening an issue as a last resort to see if someone on here can help me.
Points to note:
Disabling it and testing forward search with the built-in viewer works fine. The cursor indicates where it is supposed to be. No issues there.
Running the explicit command for forward-search on the command line with the same arguments in the json settings file works fine. Sioyek links to the exact line in the PDF and highlights it accordingly. This leads me to believe there is something happening on the VSCode latex-workshop end. Here is the command line argument that does work:
I initially thought the keybinding was not working, and changed it to something that was completely different, such as Ctrl+Cmd+Options+J (rather than the default Options+Cmd+J). Does not do anything.
I have also tried the alternate rebinding to Ctrl+Alt instead of the Cmd+Alt, and it still does not work.
I then thought this might have to do with selecting SyncTex from cursor in the left pane of latex-workshop, but I have done the same and it does not work.
Here are my external viewer settings on VSCode:
Additional notes, in case someone comes across this from Google (or ChatGPT via Bing nowadays):
assuming you have the VSCode executable added to your path and
which code
actually returns the location of the executable, which typically should be/Applications/Visual\ Studio\ Code.app/Contents/Resources/app/bin/code
. Please note the placement of the double quotes accordingly, since it is different on *nix, or could be different from what it is on the actual *nix settings on the Wiki.The corresponding setting is
prefs.config
on the Sioyek side isinverse_search_command code -r -g "%1:%2"
. That is it. It does not need thecli.js
and other flags there.Also, Sioyek does not have
--reuse-instance
as a flag, as mentioned on the Wiki. I am not sure if this is a difference between the Sioyek implementations on Windows and macOS, but it is--reuse-window
.If it helps, I installed VSCode by downloading the package and Sioyek was installed using
brew install --cask sioyek
and the installation goes to/opt/homebrew/cask/sioyek
.Beta Was this translation helpful? Give feedback.
All reactions