Add bracket indentation semantics to (* *) #1998
Open
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.
Background: ionide/ionide-fsgrammar#209 and ionide/ionide-fsgrammar#210
This comes from a comment regarding a pull request that I made on the ionide-fsgrammar repository, which removes the
(* *)
bracket pair from the "brackets" field of language-configuration.json. One issue with doing this is that we lose the bracket-like indentation that VSCode provides by default for all bracket pairs. This pull request re-adds the same semantics to the indentation rules.In other words, when I hit Enter in the following configuration, cursor location represented by the white block:
It should indent the cursor and then put the
*)
on the next line with the same indentation level as the(*
as follows:When I hit Enter with an unaccompanied
(*
:It should simply indent as follows:
Lastly, an unaccompanied
*)
should outdent. That is,should become