> When I'm on the second param, I'll delete forward to the next ","
you can't do that, else you'll delete not enough ('gra') or
too much ('baz,')
> ctrl+shift+right
It fails the moment one of the second arguments has a space or a dash. e.g default value:
def qux(bar, baz = {}, qux)
or in some languages (CSS, HTML, LISP)
The interesting reason is
why it fails: you say you want to delete 'to the next ","' but do word movement with w or ctrl+arrows. Indeed this is solved by Vintage mode, but I unfortunately found it too inconsistent with vim, and lacking a few critical features (e.g vim-surround and indent-object) for me.
Also, multiple cursors rock anyway, but if I want to apply them to a number of elements responding to a criteria and decide on a case by case basis if I want to apply then it does not work. Also it does not work when there's no code locality (i.e affected code is not visible in the same view, or spread around multiple files). The major difference with macros is that they're repeatable, while multiple cursors do the same thing at once, and once.
Also, when one vim user uses f/t too often, one should look into an object describing what he wants to really do (here [0]).
[0] http://www.vim.org/scripts/script.php?script_id=2699
I hope Sublime Text has or introduces at some point the same extendable concept of text objects as in vim.
Don't get me wrong, I'm not saying anything of this is bad per se, just that there's room for improvement.