-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Add paragraph + indenation text object/motion #1580
Comments
@archseer my mistake, I didn't mean that it would be easy from an implementation standpoint. What I meant to say was that it is very easy to unambiguously define across languages, i.e.:
|
Yes, the first implementation I want it to be in a behavior that I would like to use, but it end up being more complicated that I thought, so I guess I am just gonna port kakoune's implementation over. But lately I am busy, I really like this feature too so I guess I need to speed on this since someone is requesting it too. |
@pickfire kakoune's implementation sounds great to me. Which differences did you originally plan to implement? Honestly, the absence of this and searching with an interactive prompt are the only things that still have me occasionally opening Vim, and I'd say that's pretty impressive for an editor this young. Keep up the good work! |
When you select paragraph from the end of the file, it will select the last paragraph with previous whitespace, kakoune does not do that but vim do that. |
Also improved testing facility. Fix helix-editor#1580
Also improved testing facility. Fix helix-editor#1580
Also improved testing facility. Fix helix-editor#1580
Also improved testing facility. Fix helix-editor#1580
Also improved testing facility. Fix #1580
These are very simple to define (by whitespace) and often reflect logical groupings that are not part of a programming language's grammar (not Treesitter's domain).
I tend to put lines of code that are related together, and I do my best to indent things semantically. I think this applies to most programmers across all filetypes so it makes sense as language-agnostic functionality.
The text was updated successfully, but these errors were encountered: