if text object isn't recognized, nothing should happen

[bronson]

If the user types vix, nothing should happen. x is not a valid text object.

Vim does nothing. Atom, alas, deletes the character under the cursor.

Inspired by #680

[jacekkopecky]

This is a wider issue: vim-mode doesn't realize it's encountered an unrecognized key sequence, and cancel it. Above, it's ix in visual mode. In #760, it's ci3; therefore while in VIM ci3w behaves as w, having cancelled ci3, in vim-mode it behaves as c3w, ignoring the i. This is also part of #741.

[bronson]

So it's just a natural side effect of using multi-key keybindings? You know of any hope for fixing it? (just curious)

Binding every keypress would be a brute-force way of getting there but that might get out of hand.

'atom-text-editor.vim-mode.operator-pending-mode, atom-text-editor.vim-mode.visual-mode':
  'i x': 'vim-mode:reset-command-mode'
  'i X': 'vim-mode:reset-command-mode'
  'i y': 'vim-mode:reset-command-mode'
  'i Y': 'vim-mode:reset-command-mode'
  'i z': 'vim-mode:reset-command-mode'
  'i Z': 'vim-mode:reset-command-mode'
  etc etc etc

Sorta like you did with ctrl-r. :)

[jacekkopecky]

Hopefully there's no need for brute force here, even though I enjoyed employing it with ctrl-r. 8-)

[lee-dohm]

As stated in the README, this package is no longer maintained and is deprecated. We recommend that people use the vim-mode-plus package instead. Because of this, we are archiving this repository and closing all issues and pull requests. Thanks very much for your support and contributions!