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.

Sign up for GitHub

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

Jump to bottom

Problems with idetools parsing #274

Closed
gradha opened this issue Dec 13, 2012 · 3 comments
Closed

Problems with idetools parsing #274

gradha opened this issue Dec 13, 2012 · 3 comments
Labels
Tools

Comments

@gradha
Copy link
Contributor

gradha commented Dec 13, 2012

By using the --track parameter to encode three parameters into one, separated by commas, nimrod will have problems to parse paths with spaces or paths with commas. What would be better, to split the switch into three or fix the parsing problems as they crop up?
@gradha
Copy link
Contributor Author

gradha commented Dec 14, 2012

After adding a echo repr(p) to the compiler's service.nim:ProcessCmdLine, running a problematic command shows that the parameters are not being mangled at the commandline level: https://gist.github.com/4288524.

@zielmicha
Copy link
Contributor

Probably caused by #726.

@zielmicha zielmicha mentioned this issue Dec 9, 2013
Merged
@gradha gradha mentioned this issue Aug 5, 2014
Closed
@Araq
Copy link
Member

Araq commented Jan 28, 2015

Not an issue with nimsuggest. Nimsuggest supports "filename in quotes";line;col

@Araq Araq closed this as completed Jan 28, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Tools
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@gradha @Araq @zielmicha