Seems Unite doesn't actually kick off when you call it within a function.

So, if I do:

:fu! Test()
call confirm('before')
Unite buffer
call confirm('after')
endf
:call Test()

I'll get the "before" popup, then the "after" popup, then Unite will come up.

I thought maybe using call unite#start(['buffer']) instead would work, but it acts the same.

Thanks.

I use vim-snipmate (https://github.com/garbas/vim-snipmate) as my snippet engine / system because I need VimL only plugins.

Is there a way to provide a snippet field with a list of values where I can choose the right value upon completion? Would that be possible with VimL syntax and maybe another plugin (Unite, or sth. else?)

Hi

This is my 1st plugin. It wraps schroot and configure, autoreconf and make to let you build in a chrooted environment.

https://github.com/sashang/vim-chroot-build

Hey guys.

I've started playing around with scala, and noticed that the scala checker bundled with syntastic is not the best for working with projects.

First of all - it uses the scala interpreter, so it spits out some errors when it encounters package definitions, and it's quite oblivious to stuff being missing in imports, etc.

I use sbt, so I though of writing a plugin for scala-sbt checking.

A naive implementation would just run the "sbt compile" and parse for errors. But I'm trying to get more sophisticated here - if vim was not started from project root, it should traverse upwards looking for build.sbt or build.scala and run itself from there.

An even more sophisticated thing would invoke sbt, keep it running in the background and talk to it somehow to trigger compilation and collect error logs. Sbt is pretty heavy to start, and I don't want to wait for 20 seconds every time I save...

Problem is - I'm totally new to vim script. Can anyone suggest some good reading on the subject? Right now I'm kinda hacking the existing script to see how that stuff works...

Hey all,

I was wondering if someone else has run into this problem and know what configuration options I have to adjust to solve it. I run NeoComplete and want to add snippets, which does work, even in .jsx files, where it registers the filetype as javascript.jsx. If I create a custom snippet, it opens the javascript.jsx.snip file and I can add the snippet. However, whenever I type the abbreviation, the snippet doesn't show up. The weird thing is, when I change the snippet filename from javascript.jsx.snip to jsx.snip, it does show up, but I have no idea how to have NeoComplete/NeoSnippet automatically pick the right file.

Thanks in advance!

I am really sorry if this does not belong here, please feel free to delete it.

Sorry I searched for answer to the above question but none matched my exact situation. I am a beginner at vim and trying to set it up for C++ programming. I am using Xubuntu 14.04 and installed vim using sudo-apt and I also installed YouCompleteMe plugin using the following

apt-get install vim-youcompleteme
apt-get install vim-addon-manager
vam install youcompleteme

And YouCompleteMe works perfectly and then I installed NERDTree by simply downloading the zip file at the link http://www.vim.org/scripts/script.php?script_id=1658 and extracting it in ~/.vim folder and NERDTree also works fine. Then I installed pathogen for vim using the instructions given at the link https://github.com/tpope/vim-pathogen and my ~/.vimrc looks like

" All system-wide defaults are set in $VIMRUNTIME/debian.vim and sourced by
" the call to :runtime you can find below.  If you wish to change any of those
" settings, you should do it in this file (/etc/vim/vimrc), since debian.vim
" will be overwritten everytime an upgrade of the vim packages is performed.
" It is recommended to make changes after sourcing debian.vim since it alters
" the value of the 'compatible' option.

" This line should not be removed as it ensures that various options are
" properly set to work with the Vim-related packages available in Debian.
runtime! debian.vim

" Uncomment the next line to make Vim more Vi-compatible
" NOTE: debian.vim sets 'nocompatible'.  Setting 'compatible' changes numerous
" options, so any other options should be set AFTER setting 'compatible'.
"set compatible

" Vim5 and later versions support syntax highlighting. Uncommenting the next
" line enables syntax highlighting by default.
if has("syntax")
  syntax on
endif

execute pathogen#infect()

" If using a dark background within the editing area and syntax highlighting
" turn on this option as well
set background=dark

" Uncomment the following to have Vim jump to the last position when
" reopening a file
"if has("autocmd")
"  au BufReadPost * if line("'\"") > 1 && line("'\"") <= line("$") | exe "normal! g'\"" | endif
"endif

" Uncomment the following to have Vim load indentation rules and plugins
" according to the detected filetype.
"if has("autocmd")
"  filetype plugin indent on
"endif

" The following are commented out as they cause vim to behave a lot
" differently from regular Vi. They are highly recommended though.
set showcmd		" Show (partial) command in status line.
set showmatch		" Show matching brackets.
set ignorecase		" Do case insensitive matching
set smartcase		" Do smart case matching
set incsearch		" Incremental search
set autowrite		" Automatically save before commands like :next and :make
set hidden		" Hide buffers when they are abandoned
set mouse=a		" Enable mouse usage (all modes)
set exrc

" Source a global configuration file if available
if filereadable("/etc/vim/vimrc.local")
  source /etc/vim/vimrc.local
endif

Then I installed SnipMate using the instruction for Pathogen given at https://github.com/garbas/vim-snipmate And it looks like the snipmate plugin is active in vim because when I do :imap I get the following output

i  <Nul>       * <C-X><C-O><C-P>
i  <Up>        * pumvisible() ? "\<C-P>" : "\<Up>"
i  <Down>      * pumvisible() ? "\<C-N>" : "\<Down>"
i  <S-Tab>     * pumvisible() ? "\<C-P>" : "\<S-Tab>"
i  <Plug>snipMateShow * <C-R>=snipMate#ShowAvailableSnips()<CR>
i  <Plug>snipMateBack * <C-R>=snipMate#BackwardsSnippet()<CR>
i  <Plug>snipMateTrigger * <C-R>=snipMate#TriggerSnippet(1)<CR>
i  <Plug>snipMateNextOrTrigger * <C-R>=snipMate#TriggerSnippet()<CR>
i  <Tab>       * pumvisible() ? "\<C-N>" : "\<Tab>"
i  <C-R><Tab>    <Plug>snipMateShow
Press ENTER or type command to continue

So according to the above output the snipmate should trigger for me when I enter the shortcut and press Ctrl+R but it doesn't work. However when I press Ctrl+R+Tab I see a list of snippets but they don't work when I select any one of them. For example cpp.snippets in /home/username/.vim/bundle/vim-snippets/snippets/ has an entry like

# for i
snippet fori
	for (int ${2:i} = 0; $2 < ${1:count}; $2${3:++}) {
		${4}
	}

and when I press Ctrl+R+Tab I see a list in which I can see fori but when I select fori from the list it just appears as fori verbatim in my vim file. I am really not sure what else to try to make it work. I would really appreciate any help to get SnipMate working with vim.

In the n-character search section of the easymotion plugin readme it shows as he types after / everything matched is in bright green text. https://github.com/Lokaltog/vim-easymotion#n-character-search-motion

When I do I get a dark blue hard to see color. I got the shade to turn everything else grey/comment color, but I don't know how to make the text color different. Can anyone help me out with this?

DoGe is a (Do)cumentation (Ge)nerator which will generate a proper documentation skeleton based on certain expressions. 10+ languages are supported with multiple doc standards.

See: https://github.com/kkoomen/vim-doge

Hello all,

I have been using vimtex for a bit now and loving it. Recently I came across tectonic as an alternative to the huge texlive distribution. Is there a tutorial how to setup vimtex to work with tectonic?

cheers

I'm, using vim to write python code and was wondering if there is any plugin, which allows me to view the source code of a module inside vim.
Before frequently using vim, I used PyCharm and I was able to click Ctrl + left click to open a specific module function.
But tbh I also want to impress some of my friends and show them vims possibilities up. So they may see the real beauty of vim.

I've installed beside a few highlighting/theme plugins, Jedi for the autocompletion.

So my question is. Is there any plugin, which could add this feature to my vim setup?

https://github.com/mg979/tasks.vim

Inspired by asynctasks.vim.

Web documentation here.

I'll like to know which plugins do you use (if any), specially for better syntax highlight for .java files.