On Sun, 18 January 2015, at 12:50 am, Thomas Egerer <hakke_...@gmx.de> wrote:
> ... I often use the 'copy-line' command to copy command line > statements. When such a buffer is then pasted the statement is > immediately executed. I'm sorry if I'm not understanding exactly what you're doing, but it _sounds like_ you're copying using the command-line / keyboard and pasting with the mouse. Is it possible the problems you're seeing could be avoided with a different workflow - e.g. retrieving the contents of the buffer with `tmux show-b -b 0` or `tmux save-b -b 0 file.txt`? For example, if you're using Bash's vi-mode to edit shell commands, you can just press the escape key followed by `v` to open a new text editor window in which to edit your command. You can then read the command from file (`:r file.txt` in vi) or paste with the mouse before editing it - the saved command will be executed when you edit the text editor. I apologise if this suggestion is unhelpful, but I don't understand how you're pasting if not with the mouse, and I find that a bit incongruous. Stroller. ------------------------------------------------------------------------------ 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
