Skip to main content
Tweeted twitter.com/#!/StackUnix/status/79386939295408128
typos
Source Link
febs
  • 123
  • 1
  • 1
  • 6

I am by no means a vim power user, I am just beginning to grasp the advanced motions and commands with vim. But there's one drawback that I can't seem to get around.

I grew up with graphical programs for writing code, but I've just recently started using vim over ssh & screen to work on fairly large projects with many folders.

I'm curious what the vim masters do to work with multiple files quickly and easily. Consider a rails app as an example. Say you want to edit a controller so you run.

vim app/controllers/controller.rb 

But then you quickly want to change to editing a view or a db migration, my first instinct is to :wq:wq, return to bash to navigate to that directory and start vim again in a brand new buffer.

This is obviously flat out wrong.

I've learned about several things like:

  • The clientserver (but I don't want to use X over ssh and this seems like the only way)
  • :e to open another file by browsing, but I can't seem to do it very quickly. Tab complete really trips me up.
  • Opening an entire directory and searching through the buffers.
  • NERDTree is promising, but I really want to stay away from any graphical representation to keep forcing me to master command line navigation

I apologize for being naive, but I really want to learn the correct way to go about it even if it's heavily subjective.

What are your methods, and what would you recommend?

I am by no means a vim power user, I am just beginning to grasp the advanced motions and commands with vim. But there's one drawback that I can't seem to get around.

I grew up with graphical programs for writing code, but I've just recently started using vim over ssh & screen to work on fairly large projects with many folders.

I'm curious what the vim masters do to work with multiple files quickly and easily. Consider a rails app as an example. Say you want to edit a controller so you run.

vim app/controllers/controller.rb 

But then you quickly want to change to editing a view or a db migration, my first instinct is to :wq, return to bash navigate to that directory and start vim again in a brand new buffer.

This obviously flat out wrong.

I've learned about several things like:

  • The clientserver (but I don't want to use X over ssh and this seems like the only way)
  • :e to open another file by browsing, but I can't seem to do it very quickly. Tab complete really trips me up.
  • Opening an entire directory and searching through the buffers.
  • NERDTree is promising, but I really want to stay away from any graphical representation to keep forcing me to master command line navigation

I apologize for being naive, but I really want to learn the correct way to go about it even if it's heavily subjective.

What are your methods, and what would you recommend?

I am by no means a vim power user, I am just beginning to grasp the advanced motions and commands with vim. But there's one drawback that I can't seem to get around.

I grew up with graphical programs for writing code, but I've just recently started using vim over ssh & screen to work on fairly large projects with many folders.

I'm curious what the vim masters do to work with multiple files quickly and easily. Consider a rails app as an example. Say you want to edit a controller so you run.

vim app/controllers/controller.rb 

But then you quickly want to change to editing a view or a db migration, my first instinct is to :wq, return to bash to navigate to that directory and start vim again in a brand new buffer.

This is obviously flat out wrong.

I've learned about several things like:

  • The clientserver (but I don't want to use X over ssh and this seems like the only way)
  • :e to open another file by browsing, but I can't seem to do it very quickly. Tab complete really trips me up.
  • Opening an entire directory and searching through the buffers.
  • NERDTree is promising, but I really want to stay away from any graphical representation to keep forcing me to master command line navigation

I apologize for being naive, but I really want to learn the correct way to go about it even if it's heavily subjective.

What are your methods, and what would you recommend?

Source Link
febs
  • 123
  • 1
  • 1
  • 6

vim editing/switching between multiple files efficiently in large directory structures

I am by no means a vim power user, I am just beginning to grasp the advanced motions and commands with vim. But there's one drawback that I can't seem to get around.

I grew up with graphical programs for writing code, but I've just recently started using vim over ssh & screen to work on fairly large projects with many folders.

I'm curious what the vim masters do to work with multiple files quickly and easily. Consider a rails app as an example. Say you want to edit a controller so you run.

vim app/controllers/controller.rb 

But then you quickly want to change to editing a view or a db migration, my first instinct is to :wq, return to bash navigate to that directory and start vim again in a brand new buffer.

This obviously flat out wrong.

I've learned about several things like:

  • The clientserver (but I don't want to use X over ssh and this seems like the only way)
  • :e to open another file by browsing, but I can't seem to do it very quickly. Tab complete really trips me up.
  • Opening an entire directory and searching through the buffers.
  • NERDTree is promising, but I really want to stay away from any graphical representation to keep forcing me to master command line navigation

I apologize for being naive, but I really want to learn the correct way to go about it even if it's heavily subjective.

What are your methods, and what would you recommend?