Replies: 1 comment 3 replies
-
|
ohno ,I'm sorry that I should have modified my code directly in place just now. I meant that there was no problem(like typo) with my actual configuration, but there was a typo when I entered the github issue(I fix it in place already), and other problems were the same, as the background preview and more. (I'm a China user, and my English level is bad, sorry!!) Thanks to your help! |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Based on what you said about finding the built-in web preview feature in neovim's possibly incorrect typst configuration, I tried using the following configuration:
{ "lsp": { "tinymist": { "settings": { "exportPdf": "onSave", "outputPath": "$root/$name", "preview.background.enabled": true, "preview.background.args": [ "--data-plane-host=127.0.0.1:23635", "--invert-colors=auto" ] } } } }export pdf on save function runs well, but preview in background(which will serve on 127.0.0.1:23633) failed. If the plugin does implement backgound preview, how should I configure it?
The other question is, I know that the plugin does have very little buffer control over zed, and if this configuration works, is it possible to map code from browsers to zed? Otherwise, if the background preview is only limited to the preview function, then you only need to execute
tinymist previewin the cli, which can be quickly executed using a zed task.Beta Was this translation helpful? Give feedback.
All reactions