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

nothing works, eg: nimcheck output is run but doesn't show anything (even if there are obvious errors) #113

Closed
timotheecour opened this issue Nov 3, 2018 · 1 comment · Fixed by #114

Comments

@timotheecour
Copy link
Member

timotheecour commented Nov 3, 2018

/cc @Varriount @alehander42 any help much appreciated

Ever since I reported #99 (around july) nothing seems to work besides just syntax highlighting;
nimcheck is being run, but I'm not seeing any nimcheck errors or any other nimlime functionality
nothing shows in sublimetext console, nor in logs (even after adjusting for #112)

note : I'm getting this, but not sure it's relevant:

Error loading scope:source.coffee: Unable to find syntax file for scope source.coffee in Packages/NimLime/Syntaxes/Nim.tmLanguage

@timotheecour
Copy link
Member Author

after looking into NimLime source code I think I found the bug:

I have this in my ~/.config/nim/nim.cfg

--listFullPaths

but NimLime code assumes the messages are not absolute:
$nim_D/NimLime/nimlime_core/commands/nimcheck.py

view_name = os.path.split(view.file_name() or view.name())[1]
...
if file_name.lower() != view_name.lower():

indeed, removing --listFullPaths in ~/.config/nim/nim.cfg fixed the bug;
the better fix is to fix nimcheck.py of course

timotheecour added a commit to timotheecour/NimLime that referenced this issue Nov 3, 2018
Varriount pushed a commit that referenced this issue Nov 3, 2018
* fix behavior when using enters doc comment

* fix #113
@timotheecour timotheecour mentioned this issue Nov 6, 2018
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

Successfully merging a pull request may close this issue.

1 participant