eferred 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!
>> Indeed the libevent was the problem - I checked and it turned out that it
>> was one of the packages updat
" should take longer than one second on
> even the crappiest box, so my guess is tmux is not getting SIGCHLD until
> too late.
>
> What platform is this on? What libevent version are you using?
>
>
>
> On Sun, Feb 08, 2015 at 11:02:27PM +0200, Aleksandrina Nikolova wrote:
ld 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", there should
> be a corresponding "job died"
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" ver
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 occasionally 'test'
n 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 happy with
I guess it
makes no difference.
On 08/02/15 20:13, Nicholas Marriott wrote:
> 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:
>&g
myscript; sleep 1; done'?
>
>
> On Sun, Feb 08, 2015 at 03:28:53PM +0200, Aleksandrina Nikolova wrote:
>> 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
will get a
list of all packages updated that day and try to figure out which one's
the culprit, but I am at a loss as to what could be causing such a
behaviour.
On 08/02/15 15:23, Thomas Adam wrote:
> On Sun, Feb 08, 2015 at 03:09:49PM +0200, Aleksandrina Nikolova wrote:
>> Hi, tha
test, pid 26803
but I don't know how to interpret that.
On 08/02/15 14:56, Thomas Adam wrote:
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
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: "
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
Hi! You can rebind the key to not accept repeats. The default is (I believe)
bind -r Down select-pane -D
-r instructs it to wait for you to press Down again within a specified
time interval. Just bind it to
bind Down select-pane -D
and similarly for Up, Left, Right
Best wishes
On 14/11/14 17:26,
for your help!
On 14/11/14 16:11, Aleksandrina Nikolova wrote:
> Hi,
>
> Yes, just these two lines reproduce the flickering. I'm attaching my
> .Xresources and I don't start urxvt with any options.
>
> On 14/11/14 15:54, Nicholas Marriott wrote:
>> Is this config
l 1
>
> Also please send me your .Xdefaults/.Xresources and any flags you are
> using to start urxvt.
>
>
> On Fri, Nov 14, 2014 at 01:30:21PM +0200, Aleksandrina Nikolova wrote:
>> I did that first (inside afterwards, just for test): I shutdown the tmux
>> server, started
6:53PM +0200, Aleksandrina Nikolova wrote:
>> I just did - it does not... even when I set the default TERM for tmux to
>> xterm and start a new session, it still flickers.
>>
>> On 14/11/14 13:13, Nicholas Marriott wrote:
>>> Hmm. Can you test with TERM=xterm in urxv
t;
>>> What is TERM set to outside tmux?
>>>
>>>
>>> On Fri, Nov 14, 2014 at 11:52:31AM +0200, Aleksandrina Nikolova wrote:
>>>> Hi, thanks for replying - I'm attaching my .tmux.conf;
>>>> I tried removing it completely and restarting
ov 13, 2014 at 06:39:52PM +0200, Aleksandrina Nikolova wrote:
>> Greetings!
>>
>> I am using tmux v 1.9a running on Gentoo Linux amd64 under rxvt-unicode.
>> Whenever the cursor is on the last line (just above the tmux status
>> basr) it flickers every status-interval
Greetings!
I am using tmux v 1.9a running on Gentoo Linux amd64 under rxvt-unicode.
Whenever the cursor is on the last line (just above the tmux status
basr) it flickers every status-interval (regardless of how many seconds
it is set to and regardless if it is in alternate screen or not). This
doe
19 matches
Mail list logo
