Shortcut to open file in Vim

What I normally do is e . (e-space-dot) which gives me a browsable current directory - then I can / - search for name fragments, just like finding a word in a text file. I find that generally good enough, simple and quick.

---

I recently fell in love with fuzzyfinder.vim ... :-)

:FuzzyFinderFile will let you open files by typing partial names or patterns.

---

:find is another option.

I open vim from the root of my project and have the path set to there.

Then, I can open files located anywhere in the tree using:

:find **/filena< tab >

Tab will autocomplete through various matches. (** tells it to search recursively through the path).

---

You can search for a file in the current path by using **:

:tabe **/header.h

Hit tab to see various completions if there is more than one match.

---

Consider using CtrlP plug-in.

It is included in Janus Distributive.

Allows you to find files in the current directory, open buffers or most recently used files using "fuzzy matching" or regular expression.

---

unless I'm missing something, :e filename is the fastest way I've found.

You can use tab to autocomplete the filename as well.

---

I like the :FuzzyFinderTextMate (or Ctrl + F) on my setup. See http://weblog.jamisbuck.org/2008/10/10/coming-home-to-vim

---

I use a couple of shortcuts in my .vimrc file (exact syntax below).

They are based on the fact that in 90% of the cases, I want to open another file in the same directory as the file that I am currently editing, or in a directory that is very close in the hierarchy to that edited file.

Here's what the commands do do:

,cd : Change the current working directory to the directory that the current file you are editing is in.

,e : Opens a file with the current working directory already filled in so you have to specify only the filename.

Put these into your .vimrc:

map ,e :e <C-R>=expand("%:p:h") . "/" <CR>

map ,cd :cd %:p:h <CR>

Here's a sequence of events:

You are editing a file called test.java in "/home/prog" ,cd -> Current working directory now becomes "/home/prog" ,e -> Expands to ":e /home/prog" so that you can just fill in the file name, say test.h.

,e -> Expands to ":e /home" tab -> Cycle through subdirectories of /home enter -> cd to the directory you want say /home/prog ,e -> Expands to ":e /home/prog"

---

There's also command-t which I find to be the best of the bunch (and I've tried them all). It's a minor hassle to install it but, once it's installed, it's a dream to use.

https://wincent.com/products/command-t/

---

Use tabs, they work when inputting file paths in vim escape mode!

---

If you've got tags (and you should), you can open a file from the command line just by the name of the class or method or c function, with "vim -t DBPlaylist", and within vim with ":tag ShowList".

---

If you're editing files in a common directory, you can :cd to that directory, then use :e on just the filename.

For example, rather than:

:e /big/long/path/that/takes/a/while/to/type/or/tab/complete/thingy.rb
:sp /big/long/path/that/takes/a/while/to/type/or/tab/complete/other_thingy.c
:vs /big/long/path/that/takes/a/while/to/type/or/tab/complete/one_more_thingy.java

You can do:

:cd /big/long/path/that/takes/a/while/to/type/or/tab/complete/
:e thingy.rb
:sp other_thingy.c
:vs one_more_thingy.java

Or, if you already have a file in the desired directory open, you can use the % shorthand for the current filename, and trim it to the current directory with the :h modifier (:help :_%:) :

:e /big/long/path/that/takes/a/while/to/type/or/tab/complete/thingy.rb
:cd %:h
:sp other_thingy.c
:vs one_more_thingy.java

And, like others have said, you can tab-complete file names on the ex-line (see :help cmdline-completion for more).

---

This isn't exactly what you're looking for, but it's good in many cases (though not all).

If you VIM open and there's a name of a file in the buffer, you can put the cursor on that filename and type gf. This opens the file whose name is under the cursor in the same buffer. It's the same as

:e CTRL+r CTRL+w

---

I know three plugins that permit to open files, support auto-completion, and don't require to enter the full path name of the file(s) to open (as long as the files are under one of the directories from &path vim option):

searchInRuntime that I'm maintaining (the completion is not on :e/:find, but on split actions)

fuzzy finder as it has been already pointed out,

lookupfile.

Lately, I've seen another plugin with a similar feature, but I don't remember the name.

Soon, :find is likely support auto-completion -- patches on this topic are circulating on vim_dev mailing-list these days.

---

you can use (set wildmenu)

you can use tab to autocomplete filenames

you can also use matching, for example :e p*.dat or something like that (like in old' dos)

you could also :browse confirm e (for a graphical window)

but you should also probably specify what vim version you're using, and how that thing in emacs works. Maybe we could find you an exact vim alternative.

---

FuzzyFinder has been mentioned, however I love the textmate like behaviour of the FuzzyFinderTextmate plugin which extends the behaviour to include all subdirs.

Make sure you are using version 2.16 of fuzzyfinder.vim - The higher versions break the plugin.

---

With Exuberant ctags, you can create tag files with file information:

ctags --extra=+f -R *

Then, open file from VIM with

:tag filename

You can also use <tab> to autocomplete file name.

---

In GVIM, The file can be browsed using open / read / write dialog;

:browse {command}

{command} - open / read / write

open - Opens the file read - Appends the file write - SaveAs dialog

---

I installed FuzzyFinder. However, the limitation is that it only finds files in the current dir. One workaround to that is to add FuzzyFinderTextmate. However, based on the docs and commentary, that doesn't work reliably. You need the right version of FuzzyFinder and you need your copy of Vim to be compiled with Ruby support.

A different workaround I'm trying out now is to open all the files I'm likely to need at the beginning of the editing session. E.g., open all the files in key directories...

:args app/**
:args config/**
:args test/**
etc...

(This means I would have possibly scores of files open, however so far it still seems to work OK.)

After that, I can use FuzzyFinder in buffer mode and it will act somewhat like TextMate's command-o shortcut...

:FuzzyFinderBuffer

---