https://bugs.kde.org/show_bug.cgi?id=478528
--- Comment #2 from Christian R. <3288p...@duck.com> ---
Hi,
As i mentioned, the problem happens also OUTSIDE WSL, with the Windows version
of Kate in Windows 10. With that one, I tried
PS C:\> cd c:\'Program Files'\Kate\bin
PS C:\Program Files\Kate\bin> xmllint
lmxlint : The term 'lmxlint' is not recognized as the name of a cmdlet,
function, script file, or operable program.
what is weird is that in the Kate Powershell terminal, this error message
contains the wordxmllint
and when I copy-paste it in this email, it becomes
lmxlint
If I try the same procedure directly inside apowershell 7.4.0
window, this doesn't happen and the error message indeed contains xmllint
before and after copying in this email:
xmllint: The term 'xmllint' is not recognized as a name of a cmdlet, function,
script file, or executable program.
In the embedded terminal of the windows version of Kate, the command
PS C:\Program Files\Kate\bin> $PSVersionTable
results in
Name Value
---- -----
PSVersion 5.1.19041.3803
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.19041.3803
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
I'll stop here for now.
I will reinstall the Linux version of Kate inside the Debian WSL, and try your
suggestion there as well.
Christian R.
On 15.12.2023 06:36, Waqar Ahmed wrote:
> https://bugs.kde.org/show_bug.cgi?id=478528
>
> Waqar Ahmed <waqar....@gmail.com> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |waqar....@gmail.com
>
> --- Comment #1 from Waqar Ahmed <waqar....@gmail.com> ---
> if you type `xmllint` in terminal promt _inside_ kate, what happens?
>
> Maybe inside WSL commands need to be invoked differently.
>
--
You are receiving this mail because:
You are watching all bug changes.
