You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In vim gq{motion} reformats the lines {motion} moves over, it's handy to reformat function call when the list of arguments grows too long to fit the line. In vim, possibly due to language-specific plugins, that takes care of indentation as well so the next line is properly aligned with parenthesis and whatnot. In spacemacs it leaves the second line badly hanging which in some cases is syntax error, e.g.
call(one, two, three)
vim:
call(one, two,
three)
spacemacs:
call(one, two,
three)
I noticed that while python and haskell files get badly reformatted the indentation is properly applied in javascript, ruby and .c files. Of the previous languages I only have python, haskell, and javascript layers loaded which makes the inconsistent behaviour seem rather strange.
The text was updated successfully, but these errors were encountered:
This appears to be a difference between fill-region and fill-paragraph. Note that fill-paragraph (M-q) behaves as expected, it just doesn't accept a region. Since this issue has been open for a while and no upstream report has happend, I will close it.
In vim gq{motion} reformats the lines {motion} moves over, it's handy to reformat function call when the list of arguments grows too long to fit the line. In vim, possibly due to language-specific plugins, that takes care of indentation as well so the next line is properly aligned with parenthesis and whatnot. In spacemacs it leaves the second line badly hanging which in some cases is syntax error, e.g.
vim:
spacemacs:
I noticed that while python and haskell files get badly reformatted the indentation is properly applied in javascript, ruby and .c files. Of the previous languages I only have python, haskell, and javascript layers loaded which makes the inconsistent behaviour seem rather strange.
The text was updated successfully, but these errors were encountered: