Why ci” and ci(, ci{…. behave differently?

by

ci( is consistent with ci[, ci{ and cit and all the other <action>i<something>. Only ci' and ci" work like they do. The outliers are the quotes, here, not the brackets.

Vim doesn’t consider that quotes come in pairs while brackets do. It has an internal logic for matching pairs that works with actual pairs but not with quotes hence the difference in behavior.

You are not the first to complain about that discrepancy: this is one solution, maybe you can find others.

edit

I don’t have a deep knowledge of Vim’s internals, unfortunately, so I can only make assumptions, here.

If you ask Vim to do ci" it does its best to find a pair of double quotes but double quotes don’t go by pairs: there’s no way to tell if a " is the closing one or the opening one contrary to brackets. Because of that, Vim must make some choices. IMO, the choice that would make the most sense considering how the other members of the family work, would be to assume that the cursor is between the quotes and select from the first one to the right to the first one to the left. I can only assume that this method proved wrong in some way or didn’t work for some reason and that the other method (the current one) prevailed.

Another explanation could be that the i<something> mechanism is somehow tied to a specific subsystem (maybe the same as showmatch?) that is unable to deal correctly with quotes.

Anyway, just like you, I find this discrepancy weird and I’ve somehow internalized it and aligned my usage of <action>i" to how the others work. To the point of actually doing 2t"ci" or some variant instead of ci"!! Inefficient, I know.

Did you read :h a'? I completely forgot where I got my “limited understanding” of the issue but it was there! It says:

“Only works within one line. When the cursor starts on a quote, Vim will figure out which quote pairs form a string by searching from the start of the line.”

What I get from that is this: for some reasons unknown to us, Vim uses another mechanism for matching quotes than for the other pairs and that is why ci" is different from ciband friends. The underlying cause is not clear at all but I’m fairly certain that the big picture looks a lot like what I imagine.

To me, it looks a lot like a bug or a limitation disguised as a feature.

If you are still curious, I’d suggest you ask any further question on vim-dev.

More Related Contents:

  1. How to replace a character by a newline in Vim
  2. What is your most productive shortcut with Vim?
  3. Vim clear last search highlighting
  4. Redefine tab as 4 spaces
  5. Vim: apply settings on files in directory
  6. Indent multiple lines quickly in vi
  7. Where is my .vimrc file?
  8. Can I map Alt key in Vim?
  9. Search for selection in Vim
  10. How to paste over without overwriting register
  11. What is in your .vimrc? [closed]
  12. Copy all the lines to clipboard
  13. Can vim monitor realtime changes to a file
  14. Why does vim not obey my expandtab in python files?
  15. Mapping in vimrc causes bizarre arrow behaviour
  16. How can I change a file’s encoding with vim?
  17. Alt key shortcuts not working on gnome terminal with Vim
  18. Convert ^M (Windows) line breaks to normal line breaks
  19. Vim: insert the same characters across multiple lines
  20. How to insert text at beginning of a multi-line selection in vi/Vim
  21. Traversing text in Insert mode
  22. reformat in vim for a nice column layout
  23. Working with huge files in VIM
  24. Automatic closing brackets for Vim [closed]
  25. Remove all arbitary spaces before a line in Vim
  26. Replace tabs with spaces in vim
  27. Case preserving substitute in Vim
  28. Setting Vim whitespace preferences by filetype
  29. Vim run autocmd on all filetypes EXCEPT
  30. Cut to the system clipboard from Vim on Ubuntu

Leave a Comment