On Sun, Jun 17, 2012, at 08:46 PM, Giorgio Lando wrote: > 1) I start tmux; > 2) I launch mutt with the following key binding defined in my tmux.conf: > bind p neww -k -t:6 'mutt' > 3) I suspend my laptop to ram; > 4) I relaunch mutt with that same keybinding.
Sorry to correct myself so soon, but it seems that suspension is irrelevant here. In order to get the segfault, it is enough to launch mutt two times with that binding with the -k option, but only if the window with mutt is selected (if I switch to another window and press the keys mutt is destroyed and relaunched fine). But it happens e.g. also with htop: I launch it with neww, then I select that window, I relaunch it with neww -k over itself and tmux segfaults. Perhaps I shouldn't destroy (with -k) a selcted window? This was useful to me when mutt stalled, in order to relaunch it... But perhaps tmux should give an error instead of segfaulting? Best Giorgio ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
