The lastest update version 1.1.0 causes and issue

[newmana]

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

[vigoo]

I can't reproduce this.

• Do you have an example file?
• What stylish-haskell version are you using? (stylish-haskell --version)

[newmana]

Found the developer console:
(210) threadService.ts:207[Extension Host] stylish-haskell extension running: stylish-haskell "d:\model-ci\assembler-src\Assembler.hs"

That number is the counter for how many of the same log message and it just keeps going up...

[newmana]

To answer your questions:

• Works regardless of file,
• stylish-haskell-0.5.16.0

It may only occur on Windows - haven't been able to reproduce on OSX.

[vigoo]

Ok I'll try to reproduce it on Windows; thanks for detailed info

[JoelHobson]

Hi, I've just encountered the same issue on Windows.

I have stylish-haskell 0.7.1.0 with VS-code 1.10.2 and 0.0.8 of the stylish-haskell extension. If the extension is set to run on save, it goes into a loop of continuously saving and re-saving the edited file. I do not have autosave turned on in my editor settings.

My guess is stylish-haskell is being triggered on a save, then run on the file, then saved automatically, then run on the file again, then saved... etc. If we're lucky, it might just need to check if the file was unmodified after it runs.

[leshow]

I am also having this issue on Windows

[btipling]

I am also having this problem. You should detect that you don't run stylish haskell when you save changes made by your plugin. That seems to be the problem. I save, stylish Haskell makes changes, and then saves again. It may be that maybe that subsequent runs of stylish Haskell don't create the same output. Have you looked into this at all? It's been reported over a year ago. You even have a PR open to fix it: #8

[btipling]

I've tested #8 and it works. I added some quick instructions for how to take advantage of the fix in the PR until it's merged.

[vigoo]

Thanks for the fix! I'm on the road until Friday, will merge and release on the weekend.

…

On Tue, Jul 18, 2017, 23:52 btipling ***@***.***> wrote: I've tested #8 <#8> and it works. I added some quick instructions for how to take advantage of the fix in the PR until it's merged. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#5 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACL7CVi-2OkCaU6CqrmHT433-LHJjxCCks5sPRsXgaJpZM4IapKP> .

[btipling]

@vavans fixed it, but thank you for releasing it!