search

javigon / vim

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

iskeyword is wrong for javascript and ruby #181

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Open a javascript or ruby file with something like variable.property in it
2. In normal mode, with your cursor on the 'v', type 'viw'.

What is the expected output? What do you see instead?
Expected: the word 'variable' is selected
Actual: the whole 'variable.property' is selected

What version of the product are you using? On what operating system?
vim 7.4.86
Arch Linux 3.12.1-1

Please provide any additional information below.
Looking through the syntax files for javascript and ruby, it doesn't look like 
either set the 'iskeyword' option, so I think a default was just changed and 
it's falling through and causing this.

Original issue reported on code.google.com by randomen...@gmail.com on 22 Nov 2013 at 5:51

GoogleCodeExporter commented 9 years ago 
I cannot reproduce this on my installation. I create a new buffer with text 
"one.two", put my cursor on "two" and type viw. Only "two" is selected. I then 
":set filetype=ruby" and try again. Same result. I then ":set 
filetype=javascript" and try again. Same result again. ":set isk?" does not 
include the . in the value.

What does ":verbose set isk?" tell you? I suspect something in your config is 
setting this value, not a plugin distributed with Vim.

Original comment by fritzoph...@gmail.com on 22 Nov 2013 at 6:37

GoogleCodeExporter commented 9 years ago 
This was a plugin misbehaving, sorry: 
https://github.com/gorodinskiy/vim-coloresque/blob/0c21b1469993e610600e88e734ffe
90b9c10a514/after/syntax/css/vim-coloresque.vim#L127 . Thanks for the tip on 
:verbose. I didn't know that before, would've really helped in tracking this 
down.  Cheers,

Josh

Original comment by j...@bendyworks.com on 5 Dec 2013 at 7:40

GoogleCodeExporter commented 9 years ago 
This can be closed as NOTABUG

Original comment by j...@bendyworks.com on 5 Dec 2013 at 7:40

GoogleCodeExporter commented 9 years ago

Original comment by chrisbr...@googlemail.com on 3 Oct 2014 at 11:39