Apologies if it’s something that is already possible but I did not find how to do this.
I would be interested in running multiple tools in parallel for a given language in Kate.
In the case of Python, this would be tools compatible with LSP (jedi and ruff) but in the case of typst, it would not be.
For python, I can use python-lsp and its support for jedi and the python-lsp-ruff plugin as a workaround but this limits the capabilities of ruff. Would be it possible to run both jedi and ruff in parallel, as two separate LSPs.
In the case of typst, the problem is a bit more complex since I would like to use the “preview” feature of tinymist which is not an LSP feature.
A naive use of tinymist similar to what the configuration of other tools use (e.g. helix) does not seem to properly configure the tool to run the preview and another Kate user seems to think that this cannot work with Kate at the moment.
In this case, I would thus like to be able to run the tinymist preview command and passing it the current file, then starting a specific firefox profile that would open the associated URL.
Is there currently a way of doing either/both of these things in Kate and, if not, what would be the directions to explore to add such features?
ok, so I tested the external tool plugin, but, unless I missed something, it does seem well suited for the job.
From what I’ve seen it seems that the only option is to have the tool called when the document is saved, which is not what is should happen here.
Is there a way to configure the tool to run only once when the document is opened instead?
If not, are there alternative settings that could help with this?
Hmm, no there isn’t anything for that yet. We only have one trigger it seems: OnSave
What do you mean by document opened? When its opened the first time or when it is activated in the tab bar for e.g.,
A better way to handle this would be to have a dedicated “part” for this. Then our preview plugin would load the part and show the preview inside kate.`
What do you mean by document opened? When its opened the first time or when it is activated in the tab bar for e.g.,
I think either would be fine, though since the end of the sentence seems to be missing, I’m not entirely sure
A better way to handle this would be to have a dedicated “part” for this. Then our preview plugin would load the part and show the preview inside kate.`
what’s a “part”? is this documented somewhere, or could you point me to examples that I could look at?
A part is a library that can do something on its own and exposes a single widget that can be embedded in other apps. E.g., Konsole panel inside kate is a part. Markdown preview is another example. Ark can show text files using KTextEditor part.
