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 preview in the cli, which can be quickly executed using a zed task.
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.