Thank you for your help! I will report it as a bug on the libevent bug
tracker.
On 09/02/15 14:05, Nicholas Marriott wrote:
> Thanks. Either a bug in libevent or they have changed behaviour in a way
> that negatively impacts tmux. It doesn't sound reasonable for SIGCHLD to
> be deferred for so lo
Thanks. Either a bug in libevent or they have changed behaviour in a way
that negatively impacts tmux. It doesn't sound reasonable for SIGCHLD to
be deferred for so long so it is probably a bug.
On Mon, Feb 09, 2015 at 01:33:43PM +0200, Aleksandrina Nikolova wrote:
> Thanks for the explanation!
Thanks for the explanation!
Indeed the libevent was the problem - I checked and it turned out that
it was one of the packages updated right before the problem occurred. It
was updated to version 2.1.5 which is still not marked as stable on
amd64 (my platform). Reverting back to stable 2.0.22 mak
Never mind this, please do this instead:
rm tmux-*.log; strace -fo strace.out tmux -vf/dev/null -Ltest start\; set -qg
status-right '#(echo test)'\; set -qg status-interval 1\; new
(You may need to install strace first.)
Then wait for the problem to happen and as soon as it does then exit
tmux
Every time the status line is updated (not necessarily status-interval),
tmux looks for a "new" job. If it has been run and has output, it uses
that output. Otherwise it starts a "new" job but looks for the "old" job
(the previously finished one) for the output.
Every status-interval it wipes out
Are you tailing the tmux server log inside tmux? This is not a good test
because tmux will spin.
Please do:
rm tmux-*.log; tmux -f/dev/null -Ltest start\; set -qg status-right '#(echo
test)'\; set -qg status-interval 1\; new
Then wait (without typing into or otherwise touching the running t
Sorry, you're right, I hadn't noticed it's a different PID on one of the
lines. The 'died' message seems to refer to a previous job which started
and got an error. The log is big, here's a link:
https://dl.dropboxusercontent.com/u/30726682/tmux-server-28684.log
Why is it that some jobs start bef
The PID and jobs in these log snippets don't match up, can you show me
the full logs please?
You should see "job died" and "job error" for every PID. tmux will not
update the string shown on the status line until that happens, so there
is no way for it to change to empty with just "job error", the
Interesting (or actually weird)... Now the message shows up MOST of the
time, but still not every - it disappears every now and then... Could
this be related to job parallelization - the message waiting for another
job and thus being delayed, or not waiting for some preliminary job and
thus fai
Hmm. Do you still see it with this:
tmux -f/dev/null -Ltest start\; set -qg status-right '#(echo test)'\; set -qg
status-interval 1\; new
On Sun, Feb 08, 2015 at 09:37:45PM +0200, Aleksandrina Nikolova wrote:
> 1.9a. I just tried the "live" version, which fetches the latest sources from
> git:
1.9a. I just tried the "live" version, which fetches the latest sources
from git://git.code.sf.net/p/tmux/tmux-code - same thing, command output
shows up rarely and randomly...
On 08/02/15 21:28, Nicholas Marriott wrote:
> Hmm. What tmux version is this?
>
>
> On Sun, Feb 08, 2015 at 09:24:08PM
Hmm. What tmux version is this?
On Sun, Feb 08, 2015 at 09:24:08PM +0200, Aleksandrina Nikolova wrote:
> I'm attaching my full config (although I did test it with the minimal one as
> well). With #(echo test) as currently set in the config I see no output
> (most of the time, with only occasional
I'm attaching my full config (although I did test it with the minimal
one as well). With #(echo test) as currently set in the config I see no
output (most of the time, with only occasionally 'test' showing up)
On 08/02/15 21:12, Nicholas Marriott wrote:
So what do you see when you use "echo te
So what do you see when you use "echo test" instead?
What exactly do you have in .tmux.conf?
On Sun, Feb 08, 2015 at 08:50:15PM +0200, Aleksandrina Nikolova wrote:
> No... The script is really simple - all it does is decide what to use as an
> active pane title and output it (since I wasn't happ
No... The script is really simple - all it does is decide what to use as
an active pane title and output it (since I wasn't happy with the tmux
pane naming sometimes):
#!/usr/bin/perl
use Sys::Hostname;
chomp (my $name = `tmux display-message -p "#{pane_title}"`);
chomp (my
Is the script occasionally outputting blank lines? Because that will
clear what tmux got from the script before.
On Sun, Feb 08, 2015 at 07:57:54PM +0200, Aleksandrina Nikolova wrote:
> The script works perfectly and the length isn't an issue either (it's set to
> a much larger value than + , p
The script works perfectly and the length isn't an issue either (it's
set to a much larger value than + , plus the output shows up at random times)... What strikes me is
that while it used to work, I did not change anything about the script,
nor tmux config, nor anything else tmux related.
On
Are you sure it isn't something silly like the right-hand side being
chopped off because your status-right-length is too short?
Does the script work as expected if you run it from the shell with eg
'while :; do myscript; sleep 1; done'?
On Sun, Feb 08, 2015 at 03:28:53PM +0200, Aleksandrina Niko
I expect to see:
test
but I only see the date. The fact that it works fine on your system
maybe confirms my suspicion that the problem is not in tmux. It used to
work fine - the perl script whose output I use in the status was
displaying correctly all the time. About a month ago, I transit
On Sun, Feb 08, 2015 at 03:09:49PM +0200, Aleksandrina Nikolova wrote:
> Hi, thanks for replying. I used a minimal .tmux.conf and started a new
> server on one of the tty's. I'm attaching the logs. On thing caught my eye:
> run job 0xd1c300: echo test, pid 26803
> job write 0xd1c300: echo
Hi, thanks for replying. I used a minimal .tmux.conf and started a new
server on one of the tty's. I'm attaching the logs. On thing caught my eye:
run job 0xd1c300: echo test, pid 26803
job write 0xd1c300: echo test, pid 26803, output left 0
job error 0xd1c300: echo test, pid 26803
On Sun, Feb 08, 2015 at 12:02:39PM +0200, Aleksandrina Nikolova wrote:
> Greetings! I have set my tmux (right) status to be: "#(perl script
> outputting single line, no newline)" but I see the output of it only a
> small fraction of the times tmux updates the status. I've tried instead
> a trivi
Hi, thanks for replying! Unfortunately, the display-time option does not
seem to affect this part of the status in any way.
On 08/02/15 13:16, Patrick B. Shanahan wrote:
> * Aleksandrina Nikolova [02-08-15 05:04]:
>> Greetings! I have set my tmux (right) status to be: "#(perl script
>> outputti
Greetings! I have set my tmux (right) status to be: "#(perl script
outputting single line, no newline)" but I see the output of it only a
small fraction of the times tmux updates the status. I've tried instead
a trivial command such as "#(echo test)" and I've also tried, setting
the update inte
24 matches
Mail list logo
