types "use" statements for you
Vim script Makefile PHP
Latest commit 4113c46 Feb 5, 2017 @arnaud-lb committed on GitHub Update README.markdown
Failed to load latest commit information.
plugin Suppor for 'use function' Dec 6, 2016
tests Cleanup Dec 6, 2016
.gitignore ignore generated files Feb 21, 2016
README.markdown Update README.markdown Feb 5, 2017



vim-php-namespace is a vim plugin for inserting "use" statements automatically.


Import classes or functions (add use statements)

Automatically adds the corresponding use statement for the name under the cursor.

To use this feature, add the following mappings in ~/.vimrc:

function! IPhpInsertUse()
    call PhpInsertUse()
    call feedkeys('a',  'n')
autocmd FileType php inoremap <Leader>u <Esc>:call IPhpInsertUse()<CR>
autocmd FileType php noremap <Leader>u :call PhpInsertUse()<CR>

Then, hitting \u in normal or insert mode will import the class or function under the cursor.

new Response<-- cursor here or on the name; hit \u now to insert the use statement

Make class or function names fully qualified

Expands the name under the cursor to its fully qualified name.

To use this feature, add the following mappings in ~/.vimrc:

function! IPhpExpandClass()
    call PhpExpandClass()
    call feedkeys('a', 'n')
autocmd FileType php inoremap <Leader>e <Esc>:call IPhpExpandClass()<CR>
autocmd FileType php noremap <Leader>e :call PhpExpandClass()<CR>

Then, hitting \e in normal or insert mode will expand the name to a fully qualified name.

$this->getMock('RouterInterface<-- cursor here or on the name; hit \e now to expand the class name'

Sort existing use statements alphabetically

If you do not know how to organize use statements, (or anything else, for that matter), the alphabetical order might be a sensible choice, because it makes finding what you are looking for easier, and reduces the risk for conflicts : if everyone adds new things at the same line, conflicts are guaranteed.

This vim plugin defines a PhpSortUse() you may use in your mappings:

autocmd FileType php inoremap <Leader>s <Esc>:call PhpSortUse()<CR>
autocmd FileType php noremap <Leader>s :call PhpSortUse()<CR>

On top of that, you may want to have the dependencies sorted every time you insert one. To enable this feature, use the dedicated global option:

let g:php_namespace_sort_after_insert = 1


Using pathogen

git clone git://github.com/arnaud-lb/vim-php-namespace.git ~/.vim/bundle/vim-php-namespace

Using vim-plug

Add to vimrc:

Plug 'arnaud-lb/vim-php-namespace'

Run command in vim:


Using vundle

Add to vimrc:

Bundle 'arnaud-lb/vim-php-namespace'

Run command in vim:


Manual installation

Download and copy plugin/phpns.vim to ~/.vim/plugin/

Post installation

Generate a tag file

The plugin makes use of tag files. If you don't already use a tag file you may create one with the following command; after having installed the ctags package:

ctags -R --PHP-kinds=cfi


[universal-ctags] supports traits natively (with --php-kinds=cfit).

If you can't use universal-ctags, the --regex-php argument allows to extract traits:

ctags -R --PHP-kinds=cfi --regex-php="/^[ \t]*trait[ \t]+([a-z0_9_]+)/\1/t,traits/i"

You can also create a ~/.ctags file with the following contents:

--regex-php=/^[ \t]*trait[ \t]+([a-z0_9_]+)/\1/t,traits/i

Note that using --regex-php= is 10x slower than using universal-ctags.

Automatically updating tags

The AutoTags plugin can update the tags file every time a file is created or modified under vim.

To keep updates fast, AutoTags won't operate if the tags file exceeds 7MB. To avoid exceeding this limit on projects with many dependencies, use a separate tags file for dependencies:

# dependencies tags file (index only the vendor directory, and save tags in ./tags.vendors)
ctags -R --PHP-kinds=cfi -f tags.vendors vendor

# project tags file (index only src, and save tags in ./tags; AutoTags will update this one)
ctags -R --PHP-kinds=cfi src

Do not forget to load both files in vim:

" ~/.vimrc
set tags+=tags,tags.vendors

Key mappings

See Features section for adding key mappings.

The <Leader> key usually is \.


This was originally based on a similar script for java packages found at http://vim.wikia.com/wiki/Add_Java_import_statements_automatically (in comments).