ITERM_SESSION_ID not always unique
By jthack... on January 15, 2013 10:29 (imported from Google Code)
What steps will reproduce the problem?
- Hit cmd-T to open a tab. Run "printenv ITERM_SESSION_ID". Result is w0t0p0.
- Hit cmd-T to open another tab. Run "printenv ITERM_SESSION_ID". Result is w0t1p0.
- Switch back to first tab (w0t0p0). Close tab.
- Hit cmd-T to open another tab. Run "printenv ITERM_SESSION_ID". Result is w0t1p0.
- You now have two tabs with the same ITERM_SESSION_ID (w0t1p0).
What is the expected output?
Unique ITERM_SESSION_IDs.
What do you see instead?
Duplicate ITERM_SESSION_IDs.
If you open new tabs from the most-recently opened tabs, you don't get duplicates, but if you open a new tab from an "old" tab, you get the next numbered one up from the "old" tab number.
(I'd like to map these into unique tmux windows, so I can keep the same mosh/tmux tabbed windows open at home/work, which is how I discovered this issue).
What version of the product are you using?
iTerm2 20121224.
On what operating system?
Mac OS X 10.7.4.
Many thanks. I love iTerm2. Just brilliant!
Regards,
Jon.
Activity
Comment 4 by chrishay... on March 12, 2013 18:30
I have this same issue, it seems to me every split you do it should just keep incrementing the number. It doesn't make sense to have it start over depending on which pane you try to split.
To test, I added "export PROMPT_COMMAND="echo $ITERM_SESSION_ID" to my bashrc, then split panes up randomly. If I keep splitting linearly it will increment. By linearly I mean - if I split the first pane into 2, then I split the NEW pane, then the NEW pane again, etc.
If I split the panes, then go back and try splitting the original pane again, that's when the duplicate occurs. In my attached screenshot, I first split only vertically and you can see it increment across the right from p0 to p1, p2, p3, then for my 4th split I went back to p0 and tried a vertical split but was given p1. In this test, I would have expected p4.
Reassigned to @gnachman
