-
Notifications
You must be signed in to change notification settings - Fork 16
evil-visual-char Request #26
Comments
This has been discussed and is a little more complicated than it first seems. I can give more details, but the main problem is that magit is basically line based, and you typically can't take actions on parts of lines. With line selection, One way to do what you want already which is not "evil-like" is to enter into what I called text-mode with I can look into other options, but again this will almost surely involve introducing inconsistencies. |
Thanks for the explanation. I don't normally enter visual state when using magit commands (not familiar with the commands that operate on multiple lines in magit), so for me, entering visual state almost always means I'm trying to work with the text itself. I'll try out C-t and see how it works for me. |
One thing I was thinking about would be to have By the way, the commands the operate on lines in magit can be useful. For example, you can stage a subset of lines from a hunk. |
That's be an interesting option to try. I think there's a lot of value from being able to copy certain text while inside magit so even if it's a little awkward, it'd probably be worth adjusting to. Right now I just copy the entire text, paste it in a scratch buffer and then copy the values out of that. You're right about the stage commits. That's what I use it for too. |
It's going to be tricky to do this, because visual-line and visual-char both share the same underlying keymaps by default. Getting one set of bindings after visual-char and another after visual-line would I think involve some somewhat complicated trickery. Try the text mode thing with |
Thanks, I'll give that a shot then. |
When using (setq evil-magit-want-horizontal-movement t), sometimes (most of the time), I'd like to be able to select the text I want to yank with v, but both v and V go to evil-visual-line.
If there are no downfalls, could we get a setting to get the old 'v' functionality?
Thanks!
The text was updated successfully, but these errors were encountered: