Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Formatting not working #168

Open
deklanw opened this issue Jun 20, 2020 · 7 comments
Open

Formatting not working #168

deklanw opened this issue Jun 20, 2020 · 7 comments

Comments

@deklanw
Copy link

deklanw commented Jun 20, 2020

Just installed nim to give it a try.

Command 'Format Document' resulted in an error (An unknown error occurred. Please consult the log for more details.)

From the logs,

[2020-06-20 00:22:29.215] [exthost] [error] [kosz78.nim] provider FAILED
[2020-06-20 00:22:29.215] [exthost] [error] undefined
@danawoodman
Copy link

danawoodman commented Jul 16, 2020

I'm also unable to get formatting to work with VSCode complaining no formatter is installed for nim. Using choosenim and:

$ nim -v
Nim Compiler Version 1.2.4 [MacOSX: amd64]
Compiled at 2020-07-16
Copyright (c) 2006-2020 by Andreas Rumpf

active boot switches: -d:release
$ choosenim -v
choosenim v0.6.0 (2020-03-06 18:25:57) [macosx/amd64]
$ choosenim show
  Selected: 1.2.4
   Channel: stable
      Path: /Users/danawoodman/.choosenim/toolchains/nim-1.2.4

@iambudi
Copy link

iambudi commented Aug 25, 2020

I had the same issue on MacOS catalina, code formatting did not work at all.

Debugging the extension, getNimPrettyExecPath() pointing to the correct path /usr/local/bin/nimpretty.
Repackaged as VSIX file and installed it the formatting worked nicely.

After i remove and reinstall the extension again, suddenly it works like nothing wrong happened.
Kinda wierd tho.

@NickSeagull
Copy link

Any progress on this? I have the same issue

@LiamDobbelaere
Copy link

As a workaround you can install 0.6.4 (click on the cog next to the extension and choose "Install another version")

This seems to be an issue introduced in 0.6.5

@NickSeagull
Copy link

@platoff @endragor any chance you might accept PRs for fixing this?

@STaRDoGGCHaMP
Copy link

Note that this is fixed by #154

@hamidb80
Copy link

hamidb80 commented Feb 9, 2021

I have the same problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants