> Your first problem is assuming that tabs in Vim work like tabs in > other applications. That's very common the first time one sees tabs in > Vim. But tabs in Vim are more like a partially separate Vim instance. > Vim's tab pages allow you to do some very cool things that aren't > possible in other editors. A simple example would be to have one tab > open to edit/view a file, a separate tab to view a diff between it and > another file, and a third tab to view a diff between the current state > of the buffer and the file as it exists on-disk.
OK, this really seems like a have to get comfortable with concept of tabs in Vim first. Since it seems to be different to what I am used to in other applications. > In your specific example, what I would do instead of jumping to the > definition with CTRL-] would be to either jump to the definition in a > NEW WINDOW in the CURRENT tab with CTRL-W CTRL-], or even opening the > function definition in the PREVIEW window in the current tab with CTRL- > W }. This way, you can even see both files simultaneously rather than > needing to switch back and forth between tabs. Perhaps, I will try to avoid using tabs for now and get used to whole concept of buffers. Which leads to some more questions: 1) When working with multiple files (buffers) and switching away from modified buffer, we usually get E37. Unless one of the following is used: - :hide <command_to_switch_buffer> - :set hidden - :set bufhidden=hide - :set autowriteall Which one of these methods is preferred? 2) What tips do you have from own experience when working with multiple files? Perhaps some comments on work approach? Thanks! --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
