In article <20101113163405.ga7...@yelena.nicm.ath.cx>,
Nicholas Marriott wrote:
> send me logs and "tmux info" from as soon as it happens and i'll take a
> look
Somewhat related - 'tmux info' does not like to be redirected to a file;
it just hangs when I try that.
(It happened just then, but
In article ,
Ben Boeckel wrote:
> I've seen this with the aggressive-resize option on and only one client
> attached.
Yup, just saw this about 30 minutes after posting last night - and I do
have aggressive-resize enabled on the window that gets stuck.
--
Nicholas Riley
Try this.
Use -t $TMUX_PANE.
Note that if tmux needs the session as well it'll follow the normal
process to get it ("current" session if it contains the pane, otherwise
best session from all of those with the pane).
For example, paste-buffer takes a pane target but it needs the session
to know w
Other problem is this could be reused... maybe an ever-increasing pane
id is a better move.
On Sat, Nov 13, 2010 at 04:51:23PM +, Nicholas Marriott wrote:
> > >
> > > Also, since panes and such can move around, tracking a specific pane to
> > > interact with via scripts and such can be hard.
> >
> > Also, since panes and such can move around, tracking a specific pane to
> > interact with via scripts and such can be hard. Would it be possible to
> > have tmux inject a TMUX_PANE_ID into a pane's environment that is static
> > and unique for the life of the pane so that panes can always
Nicholas Riley wrote:
> Hi,
>
> I have been attempting to switch to tmux but keep running into a problem
> where a window doesn't update.
>
>>From time to time, when I type into a window, only the cursor position
> updates; the window contents don't. I can unfreeze the window by moving
> it
should be fixed now
i don't know whats going on with your other problem, a few other people
have seen this but nothing they have in common has struck me and never
been able to get to the bottom of it
send me logs and "tmux info" from as soon as it happens and i'll take a
look
cheers
On Sat,
Yeah this is not quite right although your fix is also wrong. Doh.
On Fri, Nov 12, 2010 at 11:52:22PM -0600, Nicholas Riley wrote:
> In article <4cde1a6b.4010...@cowan.name>,
> Micah Cowan wrote:
>
> > Not true; should be fixed in current CVS HEAD. As a workaround, detach
> > any other client
There is no tmux 1.3.1, just 1.3.
I bet you're using Debian, they have a local change to die if write()
fails in tty_raw(), which I advised against. Either it should be ignored
(as it is in tmux upstream) or it should retry on EAGAIN.
Report it to Debian package bug tracker.
On Fri, Nov 12, 201
