3 ms·

Could you please share how exactly you do the "jump to file foo.bar" functionality? That is the only part of vim I still find a bit laborious, probably because

• jb55 16y ago
  :b has smart tab completion. You can type any part of the filename and you can tab through the results. This is generally what I find myself doing when I have a lot of buffers open. Otherwise I just use minibufexpl with buffer next/prev keybinds.
  • lenni 16y ago
    But what about files that you haven't already opened?
    • xenomachina 16y ago
      :e also has tab completion. I also use ctags. Usually I want to look things up by symbol name, not filename, though it's trivially easy to make a script that generates a tags file of just filenames too. (And :tag also supports tab completion.)
• njharman 16y ago
  :e f<tab>.b<tab><return> or similar from command line often using history. After using a code base for a few hours/days I pretty much know where everything is and exactly how many chars I need to type before tab autocompletes. After I open a file once it is in my vim and or bash history which means opening it again is only a couple keystrokes. I use <ctrl>6 and multiple (3-4) non-overlapping terminals (with text mode vim) in various directories. So "jump to file foo.bar" is often look at the vim/terminal to the upper right or <ctrl>6 or :e<space>f<up><enter> Don't remember what this does excactly but it's in my vimrc and might have something to do with it. "freakin awesome file completion set wildmode=list:longest I also use this form of "history" bind '"\e[A"':history-search-backward bind '"\e[B"':history-search-forward
• stevelosh 16y ago
  PeepOpen or Command-T.