You need to make use of the key assigned for 'send-prefix', the default for
that is Ctrl+B. Ctrl + B followed by backtick, should insert a backtick in
your current pane.
I usually tend to keep the send-prefix the same as the prefix key.
unbind C-b; bind ` send-prefix
Now if you type backtick twi
As far as I know tmux 1.8 was the version which added support for
`resize-pane -Z`:
>From the changelog:
http://sourceforge.net/projects/tmux/files/tmux/tmux-1.8/
* resize-pane learnt '-Z' for zooming a pane temporarily
You might probably want to compile tmux 1.8 yourself to see if the homebrew
I think you're mistaken. People are just ignoring you as you've failed to
prove or support your point. And to be frank, you're the only problem I
(we) see here.
Rest has already been told.
On Sat, Apr 27, 2013 at 2:42 PM, Jason Timrod wrote:
> Those people who dont want to listen might find it
I had a similar issue with xclip and tmux 1.8. I did not try xclip with
previous versions of tmux, so not really sure if it was working with the
older tmux versions.
I think the problem is that xclip does not recognize that the input is from
stdin and waits indefinitely, causing tmux to hang as we
I personally use mode-mouse only for scrolling text. I do not use it for
select-pane.
For copy-mode I prefer to use keyboard keys, since it is much efficient.
If I want to select just a word, I use shift + mouse click (or double
click) and copy it into the X11 default clipboard.
On Wed, Apr 10,
Vim understands the xterm style key sequences when the TERM variable is set
to xterm*. But since tmux sets it to screen instead, vim fails to recognize
these keys. But this is easily fixable (and should be documented in the man
page if not already done IMO).
First, you need to enable the xterm-key
There was one old bug about this on pinentry-curses:
https://bugs.g10code.com/gnupg/issue1203
Are you using an older version by any chance ?
-Ashwin
On Sat, Apr 6, 2013 at 12:31 PM, Erik Johnson wrote:
> I use gpg-agent (with ssh support enabled), and when I use pinentry-curses
> from within
Adding a bit of delay using usleep between the commands (500ms), I seem to
get the expected behavior. So it looks more like some sort of timing issue.
On Fri, Apr 5, 2013 at 1:55 PM, Ashwin G wrote:
> Thanks Thomas
>
> But using '#{session_name} #{window_index} #{window_name
> Thomas Adam
> On 5 Apr 2013 21:20, "Ashwin G" wrote:
>
>> If I start a new session in the background, and use send-keys to run
>> `display-message`, I seem to get incorrect values for #I, #W, and #P.
>>
>> For example the following sample set of comm
If I start a new session in the background, and use send-keys to run
`display-message`, I seem to get incorrect values for #I, #W, and #P.
For example the following sample set of commands:
session_name="TEST"
# Window 0tmux new-session -d -s "$session_name" -n "Window_0"tmux
send-keys -t "$sessio
10 matches
Mail list logo
