Re: vim: session of "sessions"

On Wed, 11 Jul 2012, ping wrote:

> //what's my current issue then:
> now, it looks I easily run into a situation when I have 9+ screen sessions
> (or windows in GNU screen term) in a GNU screen instance, but still need some
> new ones.
> ...
> * switching beyond 9 windows is painful in screen, if you ever use it.

here is another approach to this issue.

1) multiple virtual terminal sessions: i switched to tmux from
screen/byobu last year. window navigation, for me, is a critical
requirement and it is quite straightforward in tmux. the windows i create
in tmux have unique names; therefore each window is directly addressable.
i routinely run 20+ windows in tmux. new window set creations and
destructions are done with functions, so creating a new batch of some
large number of directly addressable windows is easy. command line display
of all open windows, from any window, is also a capability i require.

2) mulptiple tabs in vim: i have run vim with 259 open tabs
simultaneously with no problems and snappy response. for navigation among
the tab pages currently displayed, i employ a homegrown function that
creates a list of each tab page currently open, and a key mapping to
switch to whatever tab page (and embedded window) that i need. this makes
working on large projects quite straightforward. moreover, when i need to
cross reference any regular expression across all open tab pages, i have
other homegrown functions that control grep sessions across all open tabs
and collate the results in a final report, displayed in a new tab page.
navigation to the relevant code portions on any of the open tabs is
handled by a key map to another function.

3) large project file sets: i maintain vim functions that serve as main
project centers for large projects. there are key files for each project
that routinely need to be accessed simultaneously, so these functions keep
a list of those critical files for each project and open them each in
separate tab pages when the project is invoked.

contact me for relevant code.

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php