Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Unknown Function: textobj#user#plugin #9

bytesource opened this Issue Nov 15, 2011 · 7 comments


None yet
4 participants

After having intalled vim-textobj-rubyblock to .vim/bundle using Vundle I get the following error on opening Vim:

Unknown Function: textobj#user#plugin
(.vim/bundle/vim-textobj-rubyblock/plugin/textobj/rubyblock.vim, line 12)

I also copied matchit.vim to .vim/macros.

As I am still relatively new to Vim, especially when it comes to interpreting error messages, I would be glad if you could tell me what went wrong here.



nelstrom commented Nov 15, 2011

Have you installed Kana's textobj-user plugin? The rubyblock textobject depends on it.

Also, you shouldn't have to install matchit manually, as it comes bundled with the Vim distribution. You just have to switch it on, by adding this line to your vimrc:

runtime macros/matchit.vim

I somehow overlooked the dependency to textobj-user. After installing this plugin, rubyblock textobject is now working as advertised! Thanks for pointing me in the right direction!

@nelstrom How exactly do I install textobj-user plugin? I add it to the .vim/bundle/vundle/plugin/textobj/ folder where also your rubyblock.vim plugin lives, but when I open a file with MacVim I get the message:

$Error detected while processing /Users/acandael/.vim/bundle/vundle/plugin/textobj/rubyblock.vim:
line   12:
E117: Unknown function: textobj#user#plugin




nelstrom commented Jul 15, 2014

@acandael Have you installed Kana's textobj-user plugin? The rubyblock textobject depends on it.


nelstrom commented Jul 15, 2014

@acandael sorry, misread your question. I currently use vundle to manage my vim plugins. Here's the relevant section that installs textobj-user and textobj-rubyblock, among others.

Hi Neil, thanks for your help, the keystrokes 'ir' and 'ar' are working now!


Maybe make this more prominent in the documentation? I missed it too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment