Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
vi key bindings: fix `"*y` #5100
I've had some issues with the
Huh, interestingly this does not seem to fix the issue completely. I've added this to my
I'm a bit confused at the moment because I don't seem to get that change to show up properly anywhere in my installation. I'm obviously doing something wrong here. This might be a working fix but I'm currently at odds with the build system or whatever.
Ooh, wow, that's not just something that doesn't work, it also shouldn't.
I think it actually did at one point - I faintly remember that we changed when something is taken as a bind function sometime in the 2.2 or 2.3 cycle - but it's quite unclean and prone to errors.
@raichoo: If you'd like, there's at least two more of these in the vi bindings, and the shared and default ones could also have some:
#bind -m insert o "commandline -a \n" down-line force-repaint #bind -m insert O beginning-of-line "commandline -i \n" up-line force-repaint # doesn't work
which even says that it doesn't work and is commented....
bind '"*P' backward-char "commandline -i ( xsel -p; echo )"
So I guess the other commands should be addressed once there is a solution for this issue. I don't see how to fix these motions as it is right now. Reading in the whole input and replacing it with the modified version doesn't seem like a feasible solution for me.