On Sep 16, 2012, at 4:46 PM, Nicholas Marriott wrote: > Hi > > I don't want to carry around backwards compatibility code, at least for > very long. So I say either: > > - No backwards compatibility.
I'm not much use as a C programmer, but if you are going to remove backwards compatibility, I would suggest adding a (required) key to the config file, something like: set -g configuration-version <value> As incompatible changes are made, the required value of the configuration version should increment, and tmux should reject configuration files that are no longer valid, and print a message to the effect. Also, of course, there should be a listing of incompatible changes in the man page. I suggest this because many many many dot-files are created by copying lines found online, and adding to old files, and in some cases people may not even understand what the lines do. This would at least catch some cases and let people know that things may not work in the expected way anymore. Ricky The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail. ------------------------------------------------------------------------------ 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
