On Mon, Sep 17, 2012 at 07:19:41PM +, 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 no
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 w
Hi
I don't want to carry around backwards compatibility code, at least for
very long. So I say either:
- No backwards compatibility.
- Fix it up in code with strcmp and remove it in no more than two
releases.
On Sun, Sep 16, 2012 at 06:48:48PM +0200, Marcel Partap wrote:
> >> First usage in
>> First usage instance is the renaming of the mode-mouse option.
> Hmm. I am not sure I'm too keen on this approach.
a) Please elaborate.
b) Do you have a better idea to warrant config file backwards compability?
c) More opinions needed!
> What happens when/if
> mode-copy-mouse also needs renami
On Sat, Sep 15, 2012 at 03:22:39PM +0200, Marcel Partap wrote:
> First usage instance is the renaming of the mode-mouse option.
Hmm. I am not sure I'm too keen on this approach. What happens when/if
mode-copy-mouse also needs renaming due to some other functionlity change?
I think rather than s
First usage instance is the renaming of the mode-mouse option.
---
trunk/cmd-set-option.c |3 ++-
trunk/options-table.c | 55
trunk/tmux.h |1 +
3 files changed, 58 insertions(+), 1 deletion(-)
diff --git a/trunk/cmd-set-option
