Hi Nicholas, On 01/18/2015 09:16 AM, Nicholas Marriott wrote: > Hi > > There is no way we are adding an option for this, sorry. Any explaination why? 'Sorry' really does not help me here. The newly introduced behavior makes the otherwise great tool less usable for the idea of being completely compatible with what you cannot be completely compatible with. I don't understand why you're ruling out to add the patch (because you didn't tell it). It would not harm anyone, and the default setting wouldn't change the default behavior of tmux at all. It would however free people (and it's not just me, trust me), from the burdon of rebasing the patch again and again on top of each new tmux release.
> Does the current behaviour match vi(1)? This is like comparing pears and apples. vi(1) is an editor while tmux is a terminal multiplexer with the option of copying text to buffers. It makes great sense to copy newlines within a block of selected text. It does not make sense to copy a newline at the end of a line when copying only a *single* line or at the end of a selection (even if that is what vi does). Thomas ------------------------------------------------------------------------------ New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet _______________________________________________ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
