e-zz
commented
8 months ago Hi there, I might be able to help. But before asking for any other information from you, I would suggest to check few things.
- Did you choose the correct editor in the plugin settings?
； (I use the stable version of VSCode)
- Did you try to open a page that had not been created yet, like an empty journal page? Be sure to try again with a valid page (existent on disk).
- If there is still warning about
something doesn't exist, please check the VSCode windows setting. The "safest" way in this case is to open in a new windows for each page.
Hope this helps. And please leave any further question here. I will try to look into it when I have time.
Previously I have had the patched plugin (as per issue #7) in order to open current page in VSCode and the patch has worked well.
After updating the plugin from the patched 0.0.5 to the official version 0.0.7 I cannot open current page any more so I think its the same path problem that was reported in issue #7 even though the author believes it was fixed.
For now I am sticking with the patched version until the problem is resolved.
This is a great plugin (thanks!!) .. I have included the plugin folder that you need to pop into ~/.logseq/plugins folder as a workaround.
logseq-open-in-code.zip