Marco,
I do something similar in setting up new tmux sessions. There may be a more
elegant way but I've not seen it.
To name the session you can do the following…
> tmux new-session -s foo -d
> tmux new-window -t foo -n "Editor"
> tmux send-keys -t foo vim C-m
> tmux new-window -t foo -n "Top" m
I have seen this as well with the same client and tmux version. I'm using a
local tmux server.
-Adrian
On May 10, 2013, at 5:59 AM, Mischa Peters wrote:
> Hi All,
>
> Since the upgrade from tmux 1.7 to tmux 1.8 I have terminal issues when
> attaching or detaching from tmux.
> As soon as I at
I use Terminal.app + bash + MacVim + tmux daily. Here are some suggestions.
Startup
Not sure what you're referring to in regards to extra steps. You can setup
iTerm or Terminal.app to start tmux as your default shell via a new profile.
You can also launch it with a simple "tmux" command if you a
tmux names are a not well understood feature it seems. A few details…
#T (Pane Title) is not used anywhere by default. You can manually add it to the
status line.
#W (Window Name) is what's displayed in the status line by default.
These names can be set in tmux or using escape sequences. The tmu
It occurs once in a great while with xterm-color.
-Adrian
On Nov 21, 2012, at 4:18 PM, Adrian Luff wrote:
> tmux should catch the escape sequence consistently but I seem to have found a
> race condition case where it doesn't. Adding...
>> export PROMPT_COMMAND="${PROMPT_
Doctor Who
On Dec 6, 2012, at 10:17 AM, Nicholas Marriott
wrote:
> What about TERM=vt220? It may not have colour but don't worry about
> that.
>
>
> On Thu, Dec 06, 2012 at 07:59:32AM -0800, Adrian Luff wrote:
>> It does still occur with TERM=iTerm.app. In fact it s
Nov 27, 2012 at 12:35:49PM -0800, Adrian Luff wrote:
>> export TERM='xterm-256color'
>> -Adrian
>> On Nov 27, 2012, at 12:23 PM, Nicholas Marriott
>> <[1]nicholas.marri...@gmail.com> wrote:
>>
>> What is TERM set to in all terminals o
export TERM='xterm-256color'
-Adrian
On Nov 27, 2012, at 12:23 PM, Nicholas Marriott
wrote:
> What is TERM set to in all terminals outside tmux?
>
>
> On Tue, Nov 27, 2012 at 10:14:16AM -0800, Adrian Luff wrote:
>> This occurs in the Mac OS X 10.8.2 Terminal.
This occurs in the Mac OS X 10.8.2 Terminal.app and iTerm2.
It does not occur in uxterm (via xQuartz).
If I hold enter in uxterm I do see the issue in grouped sessions on the other
two terminals (but not in uxterm).
-Adrian
On Nov 27, 2012, at 9:56 AM, Nicholas Marriott
wrote:
> What termin
by not issuing the PROMPT_COMMAND but it seems like a
bug is hiding here somewhere.
-Adrian
On Nov 27, 2012, at 8:00 AM, Nicholas Marriott
wrote:
> Does this stop happening if you take away the #() from your
> status-left/right?
>
>
> On Wed, Nov 21, 2012 at 04:18:
tmux should catch the escape sequence consistently but I seem to have found a
race condition case where it doesn't. Adding...
> export PROMPT_COMMAND="${PROMPT_COMMAND}; printf '\e]2;%s\e\\'
> \"${HOSTNAME/.*}\""
to the bash shell while inside tmux causes the status line to be printed on the
cur
{PWD_URL}"
> else # In tmux
> printf '\ePtmux;\e\e]7;%s\e\\' "${PWD_URL}"
> fi
> }
Hopefully this will save the next user some time.
-Adrian
On Nov 17, 2012, at 1:40 PM, Adrian Luff wrote:
> I'm trying to use escape sequences to se
I'm trying to use escape sequences to set my xterm-title-compabile terminal's
title from inside tmux. From a non-tmux shell the following works successfully:
> echo -ne "\e]2;Title\e\\"
According to the 1.6 changelog I need to add a DCS sequence (\eP) followed by
"tmux" to passthrough escape seq
cause I do not have X. If I had to venture a guess,
> it is probably FBterm,
>
> Thanks again.
>
> standard glitch: http://i.imgur.com/wQsJ1.png
> after a status bar enable + disable cycle: http://i.imgur.com/fQ11i.png
> with unicode turned on in .tmux.conf: http://imgur.com/
( /call/my/script )'
>
> ##/call/my/script##
> #!/bin/sh
> if [blah blah]; then
> echo "this"
> else
> echo "that"
>
> using printf instead of echo does not fix the problems with the glitching.
> also, my clock is already the rightmost thing
Ian,
Are you echoing using a simple text string…
set -g status-right "text"
…a system call...
set -g status-right '#( echo "text" )'
…or a terminal echo string…
$printf "\033]2;text\033\\"
...or perhaps something else?
I recall seeing something like this issue when updating elements flush to the
If you have to specify "tmux -2" then something is wrong with your environment.
That says your terminal supports 256 colors but isn't declaring it correctly.
With OS X 10.7+ and the Apple Terminal, configure "xterm-256color" support.
This is done in Preferences -> Settings -> Advanced -> Declare
Can you just use the desired characters directly in your .tmux.conf? With UTF-8
support enabled for my (Mac) terminal and in tmux.conf I am able to use
characters successfully. Here's what I mean...
.tmux.conf
> # Expect UTF-8 sequences to appear in this window
> set-window-option -g utf8 on
> #
One sure way to fix this is to use the built-in tmux scroll back function
rather than the xterm-dependent mouse wheel. To enter tmux's scollback buffer
press prefix shift-pgup (where prefix is your tmux prefix, by default ctrl-b).
Additionally, I use tmux in a similar environment (OS X with Term
19 matches
Mail list logo
