I've recreated a minimum (not) working example and attached the session restore file here. This issue appears to only occur when you have more than one window and one of them (I've only tried with the first) has a window name that starts with a number of another window. Apologies if that's unclear but hopefully the attached file makes a bit more sense and I can try and re-explain if not. I first noticed this when trying to restore a session that had a four digit number (2405) for the first window name. That window was closed and window 24 was put in it's place. In the example I've attached tmux just exits while restoring instead of closing only that window. I can upload the original session file as well if it's helpful.
I'm happy to help debug this further if it's useful. I tried to see if this was tied to the original issue mentioned above but it seems the original bug 169 has been lost in tmux's move from Sourceforge to GitHub and I was unable to figure out there Google Group / irc interface for help and unsure whether it was a tmux-ressurect or tmux bug in the first place.
Hello,
I've recreated a minimum (not) working example and attached the session restore file here. This issue appears to only occur when you have more than one window and one of them (I've only tried with the first) has a window name that starts with a number of another window. Apologies if that's unclear but hopefully the attached file makes a bit more sense and I can try and re-explain if not. I first noticed this when trying to restore a session that had a four digit number (2405) for the first window name. That window was closed and window 24 was put in it's place. In the example I've attached tmux just exits while restoring instead of closing only that window. I can upload the original session file as well if it's helpful.
I'm not sure if this is related to Issue #58 . I tried to recreate the steps at https://github.com/tmux-plugins/tmux-resurrect/issues/58#issuecomment-64970500 but they seem to work correctly. I'm utilizing tmux v3.2a .
I'm happy to help debug this further if it's useful. I tried to see if this was tied to the original issue mentioned above but it seems the original bug 169 has been lost in tmux's move from Sourceforge to GitHub and I was unable to figure out there Google Group / irc interface for help and unsure whether it was a tmux-ressurect or tmux bug in the first place.
tmux.conf number.txt
Sincerely, Michael