134

I have a plugin (FindFile.vim) that needs to run :FindFileCache . whenever I start vim to gather a file cache for quick opening.. I have to run this every time I start vim though.

How might I write a command that runs once, every time that vim starts up?

tester
  • 22,441
  • 25
  • 88
  • 128

6 Answers6

168

The best place to keep your configuration stuff is in your .vimrc file. However, it's sourced too early, check :h startup:

At startup, Vim checks environment variables and files and sets values
accordingly.  Vim proceeds in this order:

1. Set the 'shell' and 'term' option                *SHELL* *COMSPEC* *TERM*
2. Process the arguments
3. Execute Ex commands, from environment variables and/or files *vimrc* *exrc*
4. Load the plugin scripts.                                 *load-plugins*
5. Set 'shellpipe' and 'shellredir'
6. Set 'updatecount' to zero, if "-n" command argument used
7. Set binary options
8. Perform GUI initializations
9. Read the viminfo file
10. Read the quickfix file
11. Open all windows
12. Execute startup commands

As you can see, your .vimrc will be loaded before plugins. If you put :FindFileCache . in it an error will occur, since that command does not exist yet. (It will exist once the plugin is loaded in step 4.)

To solve this, instead of executing the command directly, create an auto-command. Auto-commands execute some command when an event occurs. In this case, the VimEnter event looks appropriate (from :h VimEnter):

                                                    *VimEnter*
VimEnter                    After doing all the startup stuff, including
                            loading .vimrc files, executing the "-c cmd"
                            arguments, creating all windows and loading
                            the buffers in them.

Then, just place this line in your .vimrc:

autocmd VimEnter * FindFileCache .
anonymite
  • 155
  • 1
  • 1
  • 7
sidyll
  • 57,726
  • 14
  • 108
  • 151
  • 3
    +1, this should be the accepted answer, it is much cleaner than creating a separate file for one command. –  Oct 12 '13 at 22:07
  • Want to add I had this break on me with E172 because I had a space after . – Caroline Jan 28 '16 at 15:47
  • tried using this approach for calling :AnsiEsc however it did not really have the desired effect - any chance you know how to detect if a command such as :AnsiEsc has been run before? – serup Oct 24 '16 at 07:40
  • 1
    This can solve many problems thank you so much for creating this post. – SdSaati Aug 28 '20 at 06:55
117

There is also the -c flag of vim. I do this in my tmuxp config to have vim start with a vertical split:

vim -c "vnew"

At least with neovim you can also open a file at the same time:

nvim -c "colorscheme mustang" some_file
djangonaut
  • 7,233
  • 5
  • 37
  • 52
  • 8
    Thanks, this is what I was looking for. Sometimes, I just need to run a temporary startup command like split as you've shown, and do not need to store this in my vimrc file – verboze Apr 16 '15 at 20:27
  • This can't open a file: `vim -c ':colo default' test.txt` – van abel Jan 26 '18 at 04:20
  • 1
    Perfect for me too - I'm using `xolox/vim-notes` and I want a fish function that opens Vim with a new note ready to go. – wsams Jun 05 '18 at 17:05
  • I use it to start the vim help when I need it in a separate window: `vim -c 'help | only'` or short: `vim -c'h|on'` - this start vim with the help and afterward executes `:only` to make it a single window – MacMartin May 06 '21 at 06:24
  • Multiple commands can be chained by repeating the '-c' option as follows:```vim -c "command1" -c "command2"``` – Claudiu Mar 11 '22 at 07:03
13

Create a file named ~/.vim/after/plugin/whatever_name_you_like.vim and fill it with

FindFileCache .

The order in which scripts are read and executed in the vim directories is described in :help 'runtimepath'

Benoit
  • 76,634
  • 23
  • 210
  • 236
3

To get even later than other answers but still just after startup, use a timer in .vimrc. For example, this code in .vimrc waits half a second after startup before setting a variable.

function DelayedSetVariables(timer)
    let g:ycm_filetype_blacklist['ignored'] = 1
endfunction
let timer=timer_start(500,'DelayedSetVariables')

(The variable in the example is the blacklist from YouCompleteMe plugin. I assume, the plugin starts up some other process asynchronously which then creates variables, but is not quite ready by the time vim has started. The variable does not exist when I try to set it in .vimrc, an after file, or VimEnter event. This is specific to my Windows system somehow, YCM documentation says .vimrc should work for setting options.)

lessthanideal
  • 1,084
  • 13
  • 14
2

You can run vim file.txt "+:FindFileCache ."

Prakhar de Anand
  • 141
  • 1
  • 5
1

Put FindFileCache in your .vimrc.

Autload commands are different and will not work for your scenario.

matpie
  • 17,033
  • 9
  • 61
  • 82