vigoo / stylish-haskell-vscode Goto Github PK

Steps to reproduce:
1/ Install lastest Visual Studio Code,
2/ Open file,
3/ Change something,
4/ Hit save,
5/ Goes into the loop.

There is Open VSX Registry for VSCode extensions. It's an open-source alternative to the most popular VSCode marketplace. Some Linux distributions (at least Archlinux) package VSCode to use Open VSX registry by default. People using these distributions may have hard time figuring out why the vigoo.stylish-haskell extension can't be found. I think the best solution is to support both registries and upload the extension to Open VSX. Could you please do that?

stylish-haskell: c:\Users\...\Open: openFile: does not exist (No such file or directory)

(Filename is C:\Users\...\Open Source\...)

I like having the ability to manually run stylish-haskell from vscode, but it would be nice if I could use the brittany integration from the vscode-hie-server plugin for the default "format document" command. Would it be feasible to add an option to support this scenario?

There was some talk about similar things here: microsoft/vscode#11609

Thanks!

When putting a .stylish-haskell.yaml file at the root of the project, and then using the Run: stylish-haskell command on a file, I get an output that does not use the project wide settings, and differs with manually running stylish-haskell file on the same file.

Changing the setting "Stylish Haskell: Command Line" also seems to have absolutely no effect on the plugin.

Last night I was using VSCode and the stylish-haskell extension automatically reformatted my code on save.

This morning there was no automatic code formatting on save. After a bit of troubleshooting I figured out how to downgrade VSCode extensions and installed version 0.0.9 of the extension. Automatic reformatting worked again.

I'm using VSCode 1.26.1 (SHA 493869ee8e8a846b0855873886fc79d480d342de). There was no error output in the developer tools javascript console, so I am unsure of how to proceed in debugging.

On syntax error in my code, Output pane arises with Stylish error message. The focus is there, and I have to use mouse to return to editing and fix the error.

I suggest to use Errors pane to show errors from Stylish.

I save pretty frequently and anytime I save a haskell file that has any sort of parse error in it, the style-haskell Output pane (from the bottom) opens itself up and takes away the focus from the main text editor. It says

Language.Haskell.Stylish.Parse.parseModule: could not parse <unknown>: ParseFailed (SrcLoc "<unknown>.hs" 72 1) "Parse error: ;"

and this gets really annoying since it happens on almost every save.

stylish reads its configuration from the current directory (or higher), so you must run it with proper working directory.

Running from project directory may be right solution if Code were supported multiple project windows. But currently it doesn't, and many people open a projects directory that is higher than any project directory.

So the only solution I see is to run stylish from the file's own directory.

Currently stylish is run from nowhere, so it is unable to use project config. I consider it a bug.