https://bugs.kde.org/show_bug.cgi?id=416320
--- Comment #5 from Maciej Libera <maciej.lib...@fastmail.com> ---
That was quick :)
So for running on new text buffer, it works without workaround.
By default I only saw two git tools, which is understandable, because other use
*nix tools.
I tried JSON and XML format. I kind of cheated, because I just used Windows
Subsystem for Linux: changed "Executable" to 'wsl' and move old value of the
field to the beginning of "Arguments". E.g. for JSON format this is:
Executable: wsl
Arguments: jq '.' %{Document:FileName}
This will of course work only if someone enable WSL and install some distro on
it with required tools.
I also modified "Google Selected Text":
Executable: cmd
Arguments: /C start ""
"https://www.google.com/search?q=%{Document:Selection:Text}";
Yes, there are empty "" - it means no command, so OS will choose default
program.
Strange thing is that it breaks on '&'. So if you try to search for e.g. 'some
text & some other stuff' it will search only for 'some text '. I do not know
why or whether it is something with Kate, my configuration or Windows. That is
why I did not reported a bug for this, but I can if you wish of course. Note,
that spaces are not problematic which (I guess?) means the text is correctly
put in "".
One thing to note is that Kate is converting text in %{Document:Text} to
default Windows encoding, which, surprisingly, is not UTF-8. This is probably
the right thing to do and something to keep in mind.
--
You are receiving this mail because:
You are watching all bug changes.
