add support from table / record transposition #28
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
this is to make sure *transpose* does not mutate the cell under the cursor, but rather the whole view.
now, it is not only used with INSERT mode, so it makes more sense to make it more general.
this will be fixed in later commits of course, but it's not really less correct than passing the input value directly and it allows to see the effect of the transposition.
this let the "record" tests pass.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
this PR adds the ability to tranpose the current view, if it's a table or a record, just as the built-in
transposecommand does.the default binding is
t.the transposition is an involution, i.e. it is its self inverse, meaning that applying the tranposition twice give you back the original data.