Fix: 'a'-kind textobjs never operated linewise #3195
Closed
+1
−2
Conversation
This file contains hidden or 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
The intention in lervag#365 (comment) is that non-inline regions should be linewise. So I don't know why l:is_inline is a requirement on top of l:linewise
Contributor
Author
|
Closing, as it seems that I'm just confused. But I would comment that (without this PR) I never seem to get linewise operator behaviour, even though the environments are cleanly separated into lines, and |
Owner
Hmm. To be honest, this is something I haven't look into or even used in quite a while. Feel free to open an issue where you explain how to reproduce the unexpected behaviour. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The intention in
#365 (comment) is that non-inline regions should be linewise.
So I don't know why
l:is_inlineis a requirement on top ofl:linewise