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
Ex commands: blockwise, charwise range #22297
Comments
This is in vim's todo.txt I believe. vim/vim#3292 It is relevant for all commands, not just Closest thing I could find is: https://github.com/vim/vim/blob/1d87e11a1ef201b26ed87585fba70182ad0c468a/runtime/doc/todo.txt#L5743-L5745
But this could be for all commands, not just
Note that charwise is different than blockwise. Would need some way to disambiguate that. |
:
to execute a command over that block
otoh, it's pretty easy to make a plugin that :
Not perfect but could be pretty useful. |
You can use the |
That is a special case for search and |
Good catch about blockwise selection being different from charwise selection. Maybe something like I'm not fully up to date on nvims goals, does something like this belong in the main program or is it more suitable for a plugin? I don't have experience with plugins/nvim internals but would be keen to get my hands dirty |
This would probably need to be a core change |
Okay, who would I speak to in order to get an idea about what the definition of done is? Maybe this would need to be broken into a charwise and a blockwise change, although I'm not sure what your status quo is. |
Yeah, let's start with charwise first. I'd say "done" for charwise is: Proposal
|
Problem
(Originally asked about solutions here)
In vim/neovim, ranges are only line-wise. I'd like to be able to perform commands on column- and line-wise ranges. There are more examples in the Stack overflow post, but I find it odd that the vim help pages talk about line-based ranges as though column-based ranges were planned in the future:
Is there any tracking issue for the comment "In a future release ":" may work on partial lines"? If not, I felt there should be one. It would be a big help.
There is a plugin that partially solves this: vis, although it's not as ergonomic as it could be.
Expected behavior
If a block of text were selected using
ctrl-v
(or even just a part of a line of text), then pressing:
should auto-fill the partial-line range selector::`<,`>
instead of it's current behaviour, which auto-fills the line-based range selector::'<,'>
. I'm not sure if it's feasible (or possible) to migrate all line-based commands to the new selector.The text was updated successfully, but these errors were encountered: