#define is considered two words about vim-wordmotion HOT 2 CLOSED

Yes, that was added for #48. Sorry.

I'm planning to fix it so that it would only recognize hex color codes if it ends with a word boundary. Unfortunately, #define will still be treated as two words in that case (# and define).

If # were a comment marker like #this is a comment, it would be kind of weird to include it in the first word of the comment.

Hard coding #define, #ifdef, and other C preprocessor directives would veer too much into language-specific territory, which I kind of don't want to support.

There's actually an undocumented option (g:wordmotion_extra) that lets you add extra word patterns, so you can use something like:

let g:wordmotion_extra = ['^#define\>', '^#ifdef\>']

or more generally:

let g:wordmotion_extra = ['#\w\+']

I removed it from the documentation because I didn't see a lot of people using it, but if more language-specific requests come in, I'll consider adding it back.

from vim-wordmotion.

There's actually an undocumented option (g:wordmotion_extra) that lets you add extra word patterns, so you can use something like:

let g:wordmotion_extra = ['^#define\>', '^#ifdef\>']

This works. Thank you!

from vim-wordmotion.