-
Notifications
You must be signed in to change notification settings - Fork 83
The line following a let
in a do
block should not be indented.
#85
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
Comments
While this is true there is not easy way to detect that you are in a |
What's really annoying is that the indentation is often changed in cases like this where it was correct before. Is there a way to disable automatic indentation in this plugin? It makes it essentially unusable. |
I've just merged #88 which introduces a flag to disable indentation, so you can use one that suits your style better. |
Great, thanks! |
This addresses some of the grievances in neovimhaskell#85. Namely, we give users the option to change how indentation works with `let` statements. Current behavior: -- g:haskell_indent_let let x = 0 >>>>y = 0 let x = 0 in >>>>x -- g:haskell_indent_in let x = 0 >in x -- ??? (conflated with g:haskell_indent_let) let x = 0 >>>>x New behavior: -- g:haskell_indent_no_in let x = 0 >>>>x So for example, those who omit the 'in' on the first line and any 'let' on the second line can opt to have no indentaton: --- g:haskell_indent_no_in = 0 let x = 0 fooBar x
You can actually get rid of this auto-indenting behavior (on latest master), with this new config setting: let g:haskell_indent_let_no_in = 0 (See PR #98.) |
Right now after a complete
let
statement in ado
block, a level of indentation is added for the next line:This is not expected as
let
statements indo
blocks don't needin
clauses.If this is in case the programmer wants to type in more than one assignments in a single
let
, then it is unexpected that re-indentation of the following block (using the=
key):gives me a wrong indentation that doesn't even compile:
The text was updated successfully, but these errors were encountered: