(This is my first post in this group!)
Some notes you might find helpful:
1. I'd like to second whoever recommended GNU screen. It's great, and
you should learn to use it. Note that screen has its own virtual
terminal copy and paste functionality, which is occasionally useful.
2. As far as entering a file's path is concerned, are you familiar
with wildmenu? Try ":set wildmenu". You might like it.
3. Use the X clipboard register ('*'). This will allow you to yank and
paste from one vim instance to another. It will also assist you in
integrating vim and your working environment (for instance, you'll be
able to yank text to and from Firefox).
If you'd like to use this register by default, add the following (or
something similar) to your .vimrc:
set clipboard=autoselect,unnamed
You might also like:
inoremap <C-v> <C-r>*
cnoremap <C-v> <C-r>*
(See http://vim.wikia.com/wiki/Accessing_the_system_clipboard .)
4. The vim help files seem to recommend against using 'autuchdir'. I
use the following:
autocmd BufEnter * lcd %:p:h
(See http://vim.wikia.com/wiki/Set_working_directory_to_the_current_file
.)
Also, NERD tree (as others have said) is very good.
Hope this helps.
On Jan 5, 1:01 pm, "Per Thulin" <per.thu...@valentinewebsystems.se>
wrote:
> Hello fellow vim users!
>
> I use vim for all my coding and text editing needs. Until now I've
> only used it for small projects with all files in a single folder,
> nothing complicated. However, my current job involves a lot of jumping
> around between files in very different file hierarchies, copying
> pasting etc. I've tried a few different strategies:
>
> 1. Use bash to jump around in the system and open/close new Vim
> instances when I need to edit something. This makes it easy to
> navigate the file system but doesn't work when I need to copy/paste
> content from e.g. /foo/b/c/d.txt to /bar/a/b/c/d.txt, as I need both
> these files open in the same vim instance, and to open those files as
> absolute paths is a PITA.
>
> 2. Have one Vim instance and use :Ex to navigate the file system. The
> biggest problem with this setup though is that when I've navigated to
> a different folder, I can't use :e to open a new file in this same
> folder because the working directory that :e looks at isn't affected.
>
> I think the best solution for me would be if there was a way to have
> multiple terminals where I can use bash and vim however I choose, but
> copy/paste content freely between them. I have no problems with
> multiple windows, just need to be able to copy/paste.
>
> So my question is: how do you manage long file hierarchies in vim? I
> know it's possible because I've heard about very skilled developers
> doing the same work as I do entirely in vim.
>
> Thanks!
> -Per Thulin
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
