On Mon, Sep 17, 2012 at 07:19:41PM +0000, Morse, Richard E.MGH wrote: > 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>
Nah, the configuration is line-based and not release-based, so I don't think this makes sense. > Also, of course, there should be a listing of incompatible changes in the > man page. This would mean documenting what was, and what is -- and the what was then becomes irrelevant. As it happens though, there's a CHANGES file which we can use -- and if I end up helping with the 1.7 release I will ensure that I try and add such a section on "OBSOLETE COMMANDS" or some such. Note that as it happens, there's not many options which change in such a way as to break people's configs. We do try and not do this. And even if such an option were in your .tmux.conf file, you'll see the parse errors from tmux when it loads its configuration file anyway. Kindly, -- Thomas Adam ------------------------------------------------------------------------------ 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
