search

darlingm / vim

Automatically exported from code.google.com/p/vim
0 stars 0 forks source link

langmap: should not get applied after "ci", "ca" etc #298

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. set langmap='*
2. `ci'` will stop working

A patch for this is available at:
https://github.com/blueyed/vim/compare/fix-langmap-ci?expand=1

Raw: https://github.com/blueyed/vim/compare/fix-langmap-ci.patch

(and attached)

Original issue reported on code.google.com by dhahler@gmail.com on 15 Dec 2014 at 12:37

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by dhahler@gmail.com on 15 Dec 2014 at 12:39

Attachments:

GoogleCodeExporter commented 9 years ago 
This patch is probably wrong.

I have only thought about "'" here, but with "langmap=xw", "dax" should 
probably delete a word, which means that it should get (lang)mapped?!

Original comment by dhahler@gmail.com on 15 Dec 2014 at 4:25

GoogleCodeExporter commented 9 years ago 
I've updated the patch to skip langmap only literal chars ("\"'()[]{}<>`").

Original comment by dhahler@gmail.com on 15 Dec 2014 at 5:22

Attachments:

GoogleCodeExporter commented 9 years ago 
In my opinion there is no bug.  ci' is a command and langmap applies to 
commands.  The single quote is also used as the first character of a command, 
where langmap definitely applies.  Only using langmap for some characters after 
"ci" would be inconsistent.

Original comment by brammool...@gmail.com on 7 Jan 2015 at 2:27