On 23/07/2010 1:31 p.m., Nicholas Marriott wrote:
> The last diff was slightly wrong, please test this instead.
Thank you. I will test and let you know if I have any problems.
Tim
--
This SF.net email is sponsored by
The last diff was slightly wrong, please test this instead.
This should not only fix the problem but can also be a spectacular
optimisation when tmux is running locally (not over ssh).
This makes it so that if the reader (typically xterm) cannot keep up
with the output, tmux ONLY updates its inte
don't bother with this, there is a better one coming soon
On Thu, Jul 22, 2010 at 11:15:09PM +0100, Nicholas Marriott wrote:
> Anyone seeing this or not seeing it please try this and let me know of
> any strangeness
>
>
> Index: server-client.c
>
Anyone seeing this or not seeing it please try this and let me know of
any strangeness
Index: server-client.c
===
RCS file: /cvs/src/usr.bin/tmux/server-client.c,v
retrieving revision 1.35
diff -u -p -r1.35 server-client.c
--- server
The problem has happened to me again, but I was able to fix it after it
occured.
I typed "C-b : lsc" and it returned this:
/dev/pts/4: 0 [208x62 xterm]
[0/2]
/dev/pts/5: 0 [208x62 xterm]
so I detached and from the terminal I typed:
tmux detach
yes, this is a known problem when a stale client is left behind, it used
to happen because we did not pick up HUP, but we do now
micahcowan and i started discussing this as a potential problem with ssh
before, because ssh will not know to disconnect the client (tcp will not
tell it), so tmux will
I have seen this exact issue as well.
If it happens again, is there anything I can do to help debug what the
problem could be?
tmux-1.3 and 1.4.14b-stable
Regards,
Tim
On Thu, July 22, 2010 7:59 am, Richard Morse wrote:
> This is tmux running locally.
>
> Ricky
>
> On Jul 21, 2010, at 3:58 PM,
This is tmux running locally.
Ricky
On Jul 21, 2010, at 3:58 PM, Nicholas Marriott wrote:
> over ssh or running natively?
>
> sounds like problems with SIGWINCH or TIOCGWINSZ
>
>
> On Wed, Jul 21, 2010 at 03:55:35PM -0400, Richard Morse wrote:
>> Is it related to changing the terminal size (i
over ssh or running natively?
sounds like problems with SIGWINCH or TIOCGWINSZ
On Wed, Jul 21, 2010 at 03:55:35PM -0400, Richard Morse wrote:
> Is it related to changing the terminal size (ie, the PuTTY window size) too
> quickly? I've just discovered that quickly changing the size of the
> Te
Is it related to changing the terminal size (ie, the PuTTY window size) too
quickly? I've just discovered that quickly changing the size of the
Terminal.app window can sometimes cause tmux to stop updating the screen until
the window is sized back to the size it had been...
Ricky
On Jul 21, 20
Yes, its 1.4.14b , sorry.
As I said I can't reproduce it, so I don't know exactly the sequence of
events that leads to this behavior, nor do I have this problem happening to
me now so I can answer your other questions.
However, I'll keep you posted the next time it happens.
Many thanks for your
I take it that is 1.4.14b libevent.
So are you doing anything particular when it happens? Running any
particular program?
After it freezes, can you still detach tmux? What does "C-b : lsc" say
after it happens? Does C-b r fix it?
On Wed, Jul 21, 2010 at 03:10:49PM -0400, Samer Atiani wrote:
>
libevent version: 1.4.1b-stable
tmux version: 1.2
platform: ubuntu 9.10, debian squeeze
TERM inside tmux: screen
TERM outside tmux: xterm
On Wed, Jul 21, 2010 at 2:59 PM, Nicholas Marriott <
nicholas.marri...@gmail.com> wrote:
> What tmux version, what platform is it running on, what is TERM set
What tmux version, what platform is it running on, what is TERM set to
inside and outside tmux, what version of libevent?
On Wed, Jul 21, 2010 at 02:46:26PM -0400, Samer Atiani wrote:
>Hello,
>I'm having a weird problem were tmux windows stop reacting to my
>keystrokes interactively,
14 matches
Mail list logo
