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
Calling unite from alias, how to open unite buffer in start-insert? #133
Comments
No. vexe is executed command in normal mode. |
I tried with this minimal vimrc set nocompatible
let bundles = split('unite.vim;vimshell.vim;vimproc.vim', ';')
let bundles = map(bundles, 'expand("~/.vim/bundle/") . v:val')
execute 'set rtp=' . join(bundles, ',') Then:
I looked at vexe.vim, I commented out |
It is feature now. You should not make minimal .vimrc. |
Shougo
added a commit
that referenced
this issue
Feb 27, 2014
|
I tried this change but yours is more flexible, thank you. if &ft == 'unite' && unite#get_context().start_insert
else
stopinsert
endif |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When executing vexe
:Unite directory -start-insert
won't open the unite buffer in insert mode for me, is there a work around or any way to fix thisThe text was updated successfully, but these errors were encountered: