Hmm actually this is weird because you say it only happens with
PROMPT_COMMAND set to change the title. My guess is that something is
funny with the way iTerm2 etc set the title and changing TERM is a red
herring.
Could you try this and see if it makes any difference:
diff --git a/tty.c b/tty.c
i
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_COMMAND}; printf '\e]2;
I think it is something in the xterm-256color TERM but not in vt220 that
does not behave (wrongly or rightly) as tmux expects.
Can you try with TERM=xterm-color? It's a lot simpler than
xterm-256color so if it is wrong too it'll be easier to see what is
different from vt220.
On Thu, Dec 06, 201
It does not occur with vt220 in OS X Terminal or iTerm2.
-Adrian
"You need to get yourself a better dictionary. When you do, look up 'genocide'.
You'll find a little picture of me there, and the caption'll read 'Over my dead
body'." --The Doctor from Doctor Who
On Dec 6, 2012, at 10:17 AM, Nic
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 seems to happen every
> time enter is hit, whereas before it only happened occasionally.
>
> -Adrian
>
>
It does still occur with TERM=iTerm.app. In fact it seems to happen every time
enter is hit, whereas before it only happened occasionally.
-Adrian
On Dec 6, 2012, at 4:54 AM, Nicholas Marriott
wrote:
> Try TERM=iTerm.app in iterm and see if still happens please.
>
>
> On Tue, Nov 27, 2012 a
Try TERM=iTerm.app in iterm and see if still happens please.
On Tue, 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
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.app and iTerm2.
>> It does no
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.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
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
What terminal are you using? Does this happen in xterm?
On Tue, Nov 27, 2012 at 09:40:39AM -0800, Adrian Luff wrote:
>Yes it does.
>I see "1;1H" appear as text in some cases, which looks to be the termcap
>command to reset to column 1 row 1 on the screen. If that's not being
>proc
Yes it does.
I see "1;1H" appear as text in some cases, which looks to be the termcap
command to reset to column 1 row 1 on the screen. If that's not being processed
correctly it would explain the status line being drawn incorrectly.
Here's my status-left and status-right lines (without e $() c
Does this stop happening if you take away the #() from your
status-left/right?
On Wed, Nov 21, 2012 at 04:18:28PM -0800, 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 PROM
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
14 matches
Mail list logo