Closed jasonm23 closed 8 years ago
I guess we could use a function that the user called to bind the default keys.
how about (global-drag-stuff-vertical)
and (global-drag-stuff-horizontal)
or something like that?
I think the functions should be better named to reflect what they do. For example: (drag-stuff-enable-default-keybindings)
or similar.
Would you be willing to fix this and make a pull request?
Sure, as long as the api names are signed off by you. I will try to get it done in the next couple of days.
Great. Just pick some names, I'll sure it'll be just fine. :)
Did this ever become a thing :P?
I'll need to do it still. I have a move up down extension which I put together years ago so I personally use that one still.
My initial motivation was to help other people adopt yours.
I'm not seeing anyone else complain about these keys, so it's a theoretical problem, as opposed to a pressing issue.
I wonder how many people are using this?
(Note OS X maps the meta-left / right to move cursor left / right word too, so imagine wider adoption for those users will pop this issue again.)
I do have this problem (on OSX as you guessed). Moving left only moves the word, not the cursor. All I really want is moving up and down. I guess I can try to avoid left/right entirely but it would be nice to disable the functionality.
I'm closing this and if this is a big enough issue, please open a pull request with the solution decided on above.
The up/down functionality is very useful, but
M-left
/M-right
are Readline / Emacs default binding, so the drag-left and drag-right on those bindings is extremely unwelcome.I suggest they are re-bound to keep them out of default bindings.
Users can easily override Emacs defaults themselves if they want to use them in this way.