Rasmus Thomsen

I'll work on this this evening, I suppose (at least for the client part, I don't quite get the futures related stuff yet, I suppose, I really have to plow...

Ah, alright. One thing I've noticed: When I don't start a 3rd event loop for logging to core stderr I get even more oddities, I'll open another issue about that.

You could take a screenshot via the shortcuts, either using `Shift+Print` to screenshot a certain area of the screen or `Print` to screenshot the entire screen.

I think this happens when the screen is locked and not necessarily because of hibernation (as in if your display turns off due to hibernation it also triggers this bug)

Maybe it'd be easier to just have users install vala-language-server via their distro and then have something like this where the VSCode flatpak has access: ``` #!/bin/sh flatpak-spawn --host vala-language-server...

No, it's running on the host, so it uses the host's VAPIs, available packages etc. IMHO this is favourable over having vls use the Flatpak environment though, since it's pretty...

I have set this up as following: 1. Created a `vala-language-server` script in `$HOME/.bin/vscode/vala-language-server` (any location will do though) with the following contents: ``` #!/bin/sh flatpak-spawn --host vala-language-server "$@" ```...

> @LecrisUT yes, without knowledge of compile arguments, the libraries you need will not be included. Wouldn't it be possible to just use compile_commands.json ? That should work for both...

It seems like `--dry-run` doesn't skip the `before_ each` etc. blocks and only the `it` blocks though. As such `--dry-run` takes about 2 minutes to run on my machine, whereas...

Hej, is there anything that can be done to help get this solved? What's the status of https://github.com/urdh/bandit/commit/17cb3f83221e797999d1cf4c4b569534a93c8c76, is there something I can do to help get this into master?...