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

            Bug ID: 465253
           Summary: Haskell Language Server on Kate Can Not Handle Spaces
                    in File Path
    Classification: Applications
           Product: kate
           Version: 22.12.2
          Platform: openSUSE
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: kwrite-bugs-n...@kde.org
          Reporter: piratec...@protonmail.com
  Target Milestone: ---

SUMMARY
When I try to use HLS (Haskell Language Server) on a .hs whose file path
contains a space somewhere,
the language server does not work.

STEPS TO REPRODUCE
1. Create two blank .hs files, one with a space (ex ample.hs) and one without a
space (example.hs)
2. Create an empty folder with a space in its name (fold er) and put a .hs file
into it: fold\ er/example.hs
3. Open up all three files in Kate

OBSERVED RESULT
In the first one, HLS works as expected.
In the other two I get several errors like this:
[21:29:36  LSP Server Log] haskell@/home/testuser
2023-02-04T04:29:36.242234Z | Warning | No plugin enabled for
STextDocumentDidOpen
2023-02-04T04:29:36.242743Z | Warning | No plugin enabled for
STextDocumentDocumentSymbol

and the language server does not function at all. (no syntax highlighting or
anything)
EXPECTED RESULT
HLS works on all three files.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed 20230202
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
HLS: 1.9.0.0
GHC: 9.2.5

ADDITIONAL INFORMATION
I used GHCup to install my GHC and HLS.
My User Server Settings for Haskell is:
"haskell": {
            "command": ["haskell-language-server-wrapper", "--lsp"],
            "path": ["%{ENV:HOME}/.ghcup/hls/1.9.0.0/bin"],
            "rootIndicationFileNames": ["*.cabal", "stack.yaml",
"cabal.project", "package.yaml"],
            "url": "https://github.com/haskell/haskell-language-server";,
            "highlightingModeRegex": "^Haskell$"
        },
I don't think the problem is on HLS' end because when I use their server on the
command-line like so:
haskell-language-server-wrapper

It can process all three files without problem.

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

Reply via email to