Improve support for C-style for-loops #84
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Work in progress.
While browsing around in the known-errors (bash-it) I figured out that the C-style for-loops support has several bugs:
for ((x = 0 ; x <= 100 ; x++));
is not parsed as an assignment, but a command with an error (not fixed)@maxbrunsfeld I'm not sure how I should approach the last issue. It seems variable assignment support inside for loops might be different than normal assignments. Do I have any control over white space parsing inside grammar.js?
See https://wiki-dev.bash-hackers.org/syntax/ccmd/c_for for context