-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing :endif error on launch #6
Comments
That I haven't seen before. Are you using a recent version of the https://github.com/kana/vim-textobj-user plugin? That's a key dependency. |
Yes, it's the latest version. I deleted and reinstalled all the plugins just to be sure. I'm running vim-textobj-quote as well, and it doesn't give me any trouble. |
There is a 'pattern' property in vim-textobj-user config for my sentence plugin, but I'm not able to see how that is being mis-executed command where the error is being thrown. How are you initializing the sentence plugin in your .vimrc? |
I use Vundle, so everything's sourced at the top of the vimrc. |
Are you initializing by file type, as in: set nocompatible
filetype plugin on
augroup textobj_sentence
autocmd!
autocmd FileType markdown call textobj#sentence#init()
augroup END |
Yes, I forgot that that's in there:
|
Hmm, pasting those two groups in didn't fail for me, unfortunately. Doe the error still happen if you reduce to a single block? augroup textobj_quote
autocmd!
autocmd FileType markdown call textobj#quote#init()
\ | call textobj#sentence#init()
autocmd FileType text call textobj#quote#init({'educate': 0})
\ | call textobj#sentence#init()
augroup END |
Yes, the error still happens with that block instead. And I don't have any other "autocmd FileType" lines elsewhere. |
Any chance you could post your vimrc via gist or as a public project (such as I do here: https://github.com/reedes/vim-config) ? I'll then try to reproduce the issue locally. Hopefully it'll fail where I can diagnose the cause. |
I've just installed this on my Vim 7.4 and when I open a file in Vim, I get these messages:
Not sure how best to track this one down.
The text was updated successfully, but these errors were encountered: