It's C-Space to start the selection.
On Thu, Mar 29, 2012 at 08:52:54AM +1300, Gino Lisignoli wrote:
>Hello!
>
>I can't seem to select text while in copy-mode, ctrl+b [
>Using space doesn't start the text selection
>
>.tmux.conf:
>
>set-option -g mouse-select-pane on
>s
Hello!
I can't seem to select text while in copy-mode, ctrl+b [
Using space doesn't start the text selection
.tmux.conf:
**set-option -g mouse-select-pane on
setw -g mode-mouse on
unbind o
bind-key Tab select-pane -t :.+
bind o run "tmux show-buffer | xclip -i -selection clipboard"
set -g histo
> I reckon each window should only appear in the list once regardless
> with the first match, so this is a bug.
In that case, see attached for CVS diff.
--
Jonathan Daugherty
Software Engineer
Galois, Inc.
Index: cmd-find-window.c
===
Hi
I reckon each window should only appear in the list once regardless with
the first match, so this is a bug.
On Wed, Mar 28, 2012 at 10:11:30AM -0700, Jonathan Daugherty wrote:
> Hi,
>
> If you create a new window with, e.g.,
>
> new-window -n foo
>
> and then add N panes to that window,
Hi all,
I made this Ruby script to pop out a pane into its own window and pop it
back:
https://gist.github.com/2227539
Is there a repository of useful user scripts where I can put this?
--
Le
--
This SF email is sp
Hi,
If you create a new window with, e.g.,
new-window -n foo
and then add N panes to that window, then 'find-window foo' will
always list the window N times even though (ISTM) it should only list
it once. I can see how this behavior arises naturally from how
find-window is implemented and it
OK, here is what I did to replace screen -x:
function rsc() {
CLIENTID=$1.`date +%S`
tmux new-session -d -t $1 -s $CLIENTID \; set-option destroy-unattached
\; attach-session -t $CLIENTID
}
function mksc() {
tmux new-session -d -s $1
rsc $1
}
"mksc foo" creates a always detached permanen
On Mar 28, 2012, at 1:27 AM, Wen Chen wrote:
> If you have stty erase in your shell startup files, remove it. Probably
> your terminal does not actually send ^H for erase - tmux certainly
> doesn't (it sends ^?).
Whoops, my mistake. I had exactly Wen's problem, too, and I had the solution
bac
The default is typically ^? which is correct for tmux and most terminals.
On Tue, Mar 27, 2012 at 11:27:21PM -0700, Wen Chen wrote:
>This solution works! Thank you so much! But I am kind of confused. If I
>don't set the key for erase, how can my terminal know which key is used
>for e
