https://bugs.kde.org/show_bug.cgi?id=489921

            Bug ID: 489921
           Summary: Error: ShellCheck: json parse failed with error
                    SyntaxError when opening bash files in Kate using
                    bash-language-server LSP Client
    Classification: Applications
           Product: kate
           Version: 24.05.2
          Platform: Neon
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: scripting
          Assignee: kwrite-bugs-n...@kde.org
          Reporter: info+...@virtualistic.nl
  Target Milestone: ---

SUMMARY
After installing the snap of bash-language-server, opening any bash script in
Kate will result in a strange error in the Output window of Kate
I've seen other people run into the same here error here:
 https://forum.ubuntuusers.de/topic/kate-und-lsp/

STEPS TO REPRODUCE
1. Install snap of bash-language-server: sudo snap install bash-language-server
2. Open Kate
3. Open any bash file
4. It should ask to activate the LSP Client, click: yes

OBSERVED RESULT
The Output window of Kate shows the following error:
[13:51:48  LSP Client Log] Started server bash@:
/snap/bin/bash-language-server start
[13:51:49  LSP Server Log] bash@
[Error] 11:51:49.384 ERROR ⛔️ Error while linting: Error: ShellCheck: json parse
failed with error SyntaxError: Unexpected end of JSON input
out:
err:

EXPECTED RESULT
Kate opening bash files with language linting working and not producing an
error after starting the bash-language-server plugin.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 6.1.2
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.0

ADDITIONAL INFORMATION
Also installed KDE Neon on a VM just to make sure it wasn't just happening on
my PC.
I also installed the marksman Markdown language client to see if any errors
would appear. There were no errors when opening .md files using the markdown
client.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to