each session is for some general topic, i.e. system scripts, or jupyter kernels, or to collect something that is related to the same project (e.g. development-tmux). in each session I have several repetitive tasks, which I like to have saved in separate bash_history, e.g. a complex compile command, a complex run command, a jupyter launch command which specifies a port number for that specific thing and its remembered by the shell (not by me) through the history, a series of folders each in one of the several git/svn repos I need to pull/push every now and then and I do not want to navigate to the right folder every time ...
if you are managing a system, working on a few projects, and taking care of a few minor things that requires complex commands I guess is not hard to have 14 sessions and 6 or 7 windows in each. maybe there are better ways of organizing this, but I guess we are going into the specifics of my work habits, not of tmux use : ) I just wanted to support the case for a user having 100 windows not being such an impossible case of use of tmux. On Thursday, September 3, 2020 at 1:57:36 PM UTC+2 [email protected] wrote: > > > On Sep 3, 2020, at 4:37 AM, Roberto <[email protected]> wrote: > > > > I have maybe 100 panes in 10+ sessions kept running thanks to tmux. > These are mostly to collect a separate bash history for different > repetitive, but not completely predictable, tasks. > > To me, that says you have something you could capture in one or more > parameterized scripts or functions, rather than constantly editing a > command from history. > > -- > Clint -- You received this message because you are subscribed to the Google Groups "tmux-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/tmux-users/ad1cfda3-be82-4714-95c4-b523deb50dban%40googlegroups.com.
