Extension doesn't seem to be running at all on macOS

[samuela]

When I open up a .hs file (outside of any stack/cabal project). I'm not seeing anything happen at all. The "Extensions" log in the bottom pane doesn't seem to have any output either. I'm running on macOS 10.15.4. I installed HIE via cabal based on the instructions in the README. Not sure what could possibly be wrong since there's no error messages or anything.

Version: 1.45.0-insider
Commit: 1c36d747fbf113144d3bf82b0aa3cbd290714e38
Date: 2020-04-15T05:40:02.537Z
Electron: 7.2.1
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.4.0

[fendor]

Just to clarify, there are no logs? E.g. https://github.com/alanz/vscode-hie-server#investigating-and-reporting-problems
You could also attempt to execute hie-wrapper --debug . and link the output here.

[samuela]

@fendor Yeah, my problem is that I'm not seeing "Haskell HIE (cabal)" in the Output dropdown:

[samuela]

Oh, and I do have "Trace: Server" set to "verbose" in the extension settings.

[fendor]

How did you try to start the extension? Open a haskell source file and installed the plugin?

[samuela]

How did you try to start the extension? Open a haskell source file and installed the plugin?

Yeah, exactly. I installed the extension, installed HIE according to the README, and then tried to open a haskell source file. I've tried reloading the window/restarting VSCode, but I just can't seem to get any indication that the extension is running. Is there somewhere else I could look?

[fendor]

Sorry, no idea what might have caused this.

[samuela]

Ah, so it seems that the problem is that the extension won't run unless there's a folder opened up in the "workspace". It's not enough to open a Haskell file in a new window that hasn't opened a folder yet.

[expipiplus1]

Ah, so it seems that the problem is that the extension won't run unless there's a folder opened up in the "workspace". It's not enough to open a Haskell file in a new window that hasn't opened a folder yet.

I have actually bumped into this before, is it possible to error or warn on this? Or at the least mention in the readme perhaps.