t9md

maybe because `g v` is not so perfect. My suggestion is to do next `g o` to mark word BEFORE applying `c`. That works for your case? If not, give...

Yes, this is currently limitation of vim-mode-plus. In vim-mode-plus, `escape` is not mapped to `core:cancel`. It's mapped to `vim-mode-plus:activate-normal-mode`(not in normal-mode) or `vim-mode-plus:reset-normal-mode`. This is the implementation taken over from...

How can you reproduce this? I can't. Could you share the details of reproduction steps(text/language-mode(grammar rule) and cursor-position)?.

was not easy, so postpone until I get prepared. Noticed current subword movement is not ideal, lots of spaces to improve. I understand again, directly using atom's native motion not...

https://github.com/t9md/dotfiles/blob/master/atom/keymap.cson#L320-%23L322

Also this https://github.com/t9md/dotfiles/blob/master/atom/keymap.cson#L317-%23L318 I can change subword by `c d`. `d` is mapped to `inner-subword` in my keymap. Without sacrifycing `d d`, this granular scoped keymap gives us more freedom...

Now have default keymap - `i d` is mapped to `inner-subword` - `a d` is mapped to `a-subword` - And `d` is mapped to `inner-subword` only in operator-mode, so you...

We have existing motions below. - `move-to-next-subword` - `move-to-previous-subword` - `move-to-end-of-subword` Could you explain your example movement explanation by comparing with those existing motion to make the point clear?

Can you reproduce that always? I cannot reproduce it. Here is the my environment info clipped by `Vim Mode Plus: Clip Debug Info` command. debug info ```json { "atom": "1.25.0",...

> Something bad seems to be happening in an interaction with the languageserver-rust plugin. Any reproduction steps?