Thanks! Wasn't aware of this, thus this issue can be closed.
Make each window's 'find' string local to the window in which it is entered.
When having more than one terminal window open, make it possible to set the 'find' string in one window without affecting the 'find' string in other windows. At the moment, it is necessary to re-type the string into each window as the user switches windows to find what's relevant in the focused window.
I don't understand Apple's global search criteria. Frankly, what a disaster in my opinion!
Make each window's 'find' string local to the window in which it is entered.
When having more than one terminal window open, make it possible to set the 'find' string in one window without affecting the 'find' string in other windows. At the moment, it is necessary to re-type the string into each window as the user switches windows to find what's relevant in the focused window.
I don't understand Apple's global search criteria. Frankly, what a disaster in my opinion!
Is it possible to arrange the update process to reinstate the terminal windows, tabs, sessions, layouts etc. when iTerm2 relaunches after performing an update? Since I rarely reboot my MacBook Pro, I simply close its lid when not in use, I maintain my terminal settings for long periods of time. When updates come up, I am reluctant to perform them as the restart resets everything to the default profile. I understand this is a bit tricky, but the GUI encapsulates the terminal environment, so I it should be possible to do without having to relaunch new sessions.
Is it possible to arrange the update process to reinstate the terminal windows, tabs, sessions, layouts etc. when iTerm2 relaunches after performing an update? Since I rarely reboot my MacBook Pro, I simply close its lid when not in use, I maintain my terminal settings for long periods of time. When updates come up, I am reluctant to perform them as the restart resets everything to the default profile. I understand this is a bit tricky, but the GUI encapsulates the terminal environment, so I it should be possible to do without having to relaunch new sessions.
I have a similar cpu hogging issue with build 3.1.6. CPU utilisation is very high when I have a few tabs open (on the order of 10 or so). It may be associated with a cli process I use that streams video via TCP using OpenGL, but the cpu utilisation is being reported against iTerm2.