word motion ignores '.' and '-' #547

ericfortis · 2014-02-03T06:40:59Z

How to disable the behavior where word motions ignore dots and hyphens?
Consider the following:

script.js
myVariable.on(...

The word motion includes .js as well as .on which is undesirable. For example hit * over myVariable and will look for myVariable.on

The text was updated successfully, but these errors were encountered:

chrisnicola · 2014-02-03T23:54:33Z

I've been noticing this for a few days now, it's driving my nuts. Can't think of what would be causing it though.

chrisnicola · 2014-02-05T18:12:56Z

This seems to be file dependent. My Coffeescript files are not having this problem. JS and Ruby files have the problem though.

Edit: Removing the 'ruby' group fixes this so it is one of the bundles in that group. Trying to narrow it down.

BenBergman · 2014-02-05T18:20:31Z

I sometimes see this problem in C files

struct_ptr->member_variable

chrisnicola · 2014-02-05T18:29:44Z

Removing 'tpope/vim-rails' fixes it. Not sure why though I suppose it could be a problem with vim-rails.

chrisnicola · 2014-02-05T18:47:52Z

Ideally this would happen (* is the cursor):

*something.else 
something.*else

Instead of this when vim-rails is loaded:

something.else*

or this (treats '.' as an entire word rather than part of one) when it isn't

something*.else

chrisnicola · 2014-02-05T19:38:12Z

Ok it isn't related to vim-rails. The problem doesn't occur on immediately starting Vim if I don't load vim-rails but it does eventually start to happen.

chrisnicola · 2014-02-05T19:49:40Z

Ok this time I'm pretty sure I narrowed it down properly to gorodinskiy/vim-coloresque. Take that out and the problem seems to go away. Also it seems to fix some syntax highlighting bugs. Not sure why though.

ericfortis · 2014-02-05T20:25:44Z

https://github.com/gorodinskiy/vim-coloresque/blob/master/after/syntax/css/vim-coloresque.vim

the problem is at lines 125-126

:set isk+=-
:set isk+=#
:set isk+=.

ericfortis · 2014-02-05T20:32:52Z

I mean that is what is causing the trouble, but it should be fine for css files. Please check why this plugin is sourcing for js files.

chrisnicola · 2014-02-06T17:17:38Z

Probably because JS files can also use color strings say when setting the style attribute. Ruby files same thing as @tpope pointed out, rails.vim does HTML parsing in %Q<> strings. Personally I don't need this functionality so I'm happy with simply not using it.

gonzaloserrano · 2014-02-10T16:40:29Z

Same problem here in PHP files 🐙

johntyree · 2014-02-11T05:15:23Z

This is hugely annoying. I think coloresque should come out until it can behave, if ever.

adambiggs · 2014-07-02T20:31:16Z

@spf13 I don't think 21ff737 fully solves the problem, because vim-coloresque seems to clobber the fix with a BufEnter autocmd...

The only thing that's worked for me is uninstalling coloresque.

tpope · 2014-07-03T00:55:47Z

Yes the only thing that fix will accomplish is break the current syntax highlighting if anyone reloads the vimrc.

Note that rails.vim gave up its HTML highlighting so it should no longer have an effect on its results. But Ruby files may still be affected because the plugin in question is so broken as to clobber not just the buffer local but also the global value of the option. This was explained to the author but not yet heeded. (Perhaps someone should try a pull request?)

spf13 · 2014-07-03T01:08:28Z

doh. Thanks @tpope! & @adambiggs

he's already sitting on a pull request to fix it. https://github.com/hauleth/vim-coloresque/commit/9d8fdd25f3b161e27331c1e5e5ba04d9d169e139

We should probably just remove it...or fork it and fix it.. .any volunteers?.

tpope · 2014-07-03T01:12:33Z

Note that's a partial fix; it'll still break HTML and anything that builds on it like PHP.

@keelerm84

* upstream/3.0: (22 commits) Bugfix spf13#320. vimdiff "]c" jump to next diff doesn\'t work spf13#320. Thanks the help from @keelerm84 and @pwolfram Improve the readme to show an option to configure the environment variables because they are not set by default with gVim. improve rust and puppet support Removing csapprox ... and there was rejoicing in the terminals Adding tpope/commentary Adding Toml support Improve the readme showing an option to configure the enviroment variables because they are not set by default by gVim. Remove twig from default bundles. Move beyondwords/vim-twig into PHP bundle. Don't conceal JSON syntax Don't remap <CR> for omnicomplete it causes issues Closing spf13#500. xptemplate support for scala. fixed spf13#547. Better end of word handling. Better handling of neocomplete closing. Some improvements to clipboard support Adding wildfire support.. Hit return to use it. Add tpope/vim-repeat to default install Fixed spf13#617. period is now an end of word designator fixed spf13#474 . Smaller default font on gvim remove spf13-vim 3.0 note ...

@keelerm84

* spf13-merge: (23 commits) Merge with latest spf13 Bugfix spf13#320. vimdiff "]c" jump to next diff doesn\'t work spf13#320. Thanks the help from @keelerm84 and @pwolfram Improve the readme to show an option to configure the environment variables because they are not set by default with gVim. improve rust and puppet support Removing csapprox ... and there was rejoicing in the terminals Adding tpope/commentary Adding Toml support Improve the readme showing an option to configure the enviroment variables because they are not set by default by gVim. Remove twig from default bundles. Move beyondwords/vim-twig into PHP bundle. Don't conceal JSON syntax Don't remap <CR> for omnicomplete it causes issues Closing spf13#500. xptemplate support for scala. fixed spf13#547. Better end of word handling. Better handling of neocomplete closing. Some improvements to clipboard support Adding wildfire support.. Hit return to use it. Add tpope/vim-repeat to default install Fixed spf13#617. period is now an end of word designator fixed spf13#474 . Smaller default font on gvim ...

edi9999 · 2014-11-13T16:26:05Z

Experiencing the same problem in PHP, even after removing vim-coloresque and vim-rails

edi9999 · 2014-11-13T16:31:01Z

Putting this in my .vimrc.local solves it

set isk-=-
set isk-=#
set isk-=.

UnBundle 'gorodinskiy/vim-coloresque'
UnBundle 'tpope/vim-rails'

, sourcing the file, and running :PluginClean

YuMS · 2015-02-17T01:30:16Z

Actually, some file related options are still kept in ~/.vimviews even if you have gorodinskiy/vim-coloresque removed.
You may want to clean up those views to actually solve this.

ghost · 2015-02-19T14:37:13Z

I did Nov 13, 2014 and deleted all files in ~/.vimviews.
Alas the problem still persists in my php-files.
Help and advice are highly appreciated!

Kind regards,

Ton Akveld

YuMS · 2015-02-27T14:06:12Z

You can use :verbose set iskeyword to find the evil.

ghost · 2015-02-28T11:20:01Z

Thanks YuMS.
Using your advised command, I get the following message:
iskeyword=@,48-57,_,192-255,$,-,#,.
Last set from ~~/.vimviews/~~=+Documents=+WWW=+htdocs=+avri-internet.ton.netcreators.nl=+typo3conf=+realurl_conf.php=
Press ENTER or type command to continue
The file from which iskey is called, not defined.
What now?

Help and advice are highly appreciated!

Kind regards,

Ton Akveld

YuMS · 2015-02-28T12:16:25Z

verbose set only shows the last point an option is set. As you described, iskeyword is last set in a vimview of its previous dumping. Which means you didn't find the origin script.
I suggest that you do

:1,1000bd to unload all your buffers, and close your vim
delete everything in your ~/.vimview/
open your .php file in vim and do verbose set iskeyword again to find the origin plugin who touched iskeyword
disable it or do something you like

ghost · 2015-02-28T17:25:52Z

That finally worked!
Thank you so very much, YuMS!!!

YuMS · 2015-03-06T04:09:51Z

@absynton Would mind sharing some details?

See spf13/spf13-vim#547

chrisnicola mentioned this issue Feb 5, 2014

Word motions skipping '.' in .rb and .js files tpope/vim-rails#302

Closed

BenBergman mentioned this issue Feb 6, 2014

This overides 'iskeyword' for all filetypes. gko/vim-coloresque#20

Closed

spf13 closed this as completed in 21ff737 Jun 30, 2014

spf13 reopened this Jul 3, 2014

faceleg added a commit to faceleg/dotfiles that referenced this issue May 28, 2015

Removed coloresque because of spf13/spf13-vim#547

ae36805

deiwin added a commit to deiwin/vim-dotfiles that referenced this issue Sep 14, 2015

Remove coloresque for causing issues in JS files

6f53778

See spf13/spf13-vim#547

zires mentioned this issue Jun 22, 2016

How to make * only search current word? #897

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

word motion ignores '.' and '-' #547

word motion ignores '.' and '-' #547

ericfortis commented Feb 3, 2014

chrisnicola commented Feb 3, 2014

chrisnicola commented Feb 5, 2014

BenBergman commented Feb 5, 2014

chrisnicola commented Feb 5, 2014

chrisnicola commented Feb 5, 2014

chrisnicola commented Feb 5, 2014

chrisnicola commented Feb 5, 2014

ericfortis commented Feb 5, 2014

ericfortis commented Feb 5, 2014

chrisnicola commented Feb 6, 2014

gonzaloserrano commented Feb 10, 2014

johntyree commented Feb 11, 2014

adambiggs commented Jul 2, 2014

tpope commented Jul 3, 2014

spf13 commented Jul 3, 2014

tpope commented Jul 3, 2014

edi9999 commented Nov 13, 2014

edi9999 commented Nov 13, 2014

YuMS commented Feb 17, 2015

ghost commented Feb 19, 2015

YuMS commented Feb 27, 2015

ghost commented Feb 28, 2015

YuMS commented Feb 28, 2015

ghost commented Feb 28, 2015

YuMS commented Mar 6, 2015

word motion ignores '.' and '-' #547

word motion ignores '.' and '-' #547

Comments

ericfortis commented Feb 3, 2014

chrisnicola commented Feb 3, 2014

chrisnicola commented Feb 5, 2014

BenBergman commented Feb 5, 2014

chrisnicola commented Feb 5, 2014

chrisnicola commented Feb 5, 2014

chrisnicola commented Feb 5, 2014

chrisnicola commented Feb 5, 2014

ericfortis commented Feb 5, 2014

ericfortis commented Feb 5, 2014

chrisnicola commented Feb 6, 2014

gonzaloserrano commented Feb 10, 2014

johntyree commented Feb 11, 2014

adambiggs commented Jul 2, 2014

tpope commented Jul 3, 2014

spf13 commented Jul 3, 2014

tpope commented Jul 3, 2014

edi9999 commented Nov 13, 2014

edi9999 commented Nov 13, 2014

YuMS commented Feb 17, 2015

ghost commented Feb 19, 2015

YuMS commented Feb 27, 2015

ghost commented Feb 28, 2015

YuMS commented Feb 28, 2015

ghost commented Feb 28, 2015

YuMS commented Mar 6, 2015