i see.
well thanks very much for the conversation.
i'll put that on my to-think-about list. :-)
On Mon, May 30, 2011 at 10:51 AM, Nicholas Marriott <
nicholas.marri...@gmail.com> wrote:
> On Mon, May 30, 2011 at 10:36:21AM -0700, Randy Stauner wrote:
> >how is it different than when i use th
On Mon, May 30, 2011 at 10:36:21AM -0700, Randy Stauner wrote:
>how is it different than when i use the command line inside of tmux?
>does that go straight to the server?
>how does that compare to calling "tmux command" from the shell?
>these are mostly rhetorical questions, i'm not
how is it different than when i use the command line inside of tmux?
does that go straight to the server?
how does that compare to calling "tmux command" from the shell?
these are mostly rhetorical questions, i'm not asking you to email a
dissertation on the inner workings...
just thinking about
maybe a path to consider would be to do conf-reading in a child process (a
fork)...
would that be able to wait, then when it's all done start passing values
back to the server?
not sure about that... it would definitely take some effort.
please excuse my ignorance of the greater tmux workings.
I
On Mon, May 30, 2011 at 10:17:20AM -0700, Randy Stauner wrote:
>maybe a path to consider would be to do conf-reading in a child process (a
>fork)...
>would that be able to wait, then when it's all done start passing values
>back to the server?
It would be very complicated because t
true... that would make it much more difficult.
On Mon, May 30, 2011 at 10:08 AM, Nicholas Marriott <
nicholas.marri...@gmail.com> wrote:
> The tmux server can never block
--
vRanger cuts backup time in half-while increas
The tmux server can never block
On Mon, May 30, 2011 at 10:05:30AM -0700, Randy Stauner wrote:
>yeah, my only knowledge of that stuff comes from my experience with
>perl...
>i believe perl's system() call does a fork, then in the child an exec()
>and in the parent a wait() or wait
yeah, my only knowledge of that stuff comes from my experience with perl...
i believe perl's system() call does a fork, then in the child an exec() and
in the parent a wait() or waitpid() or something along those lines...
I'd definitely need to read up on it.
I'm sure with other forking going on el
this is accurate, if-shell is asynchronous
need to fix that sometime but it ain't easy
On Sat, May 28, 2011 at 11:59:39AM -0700, Randy Stauner wrote:
>I don't know too much about tmux internals but I'm going to take a guess
>here:
>I think the if-shell command is forking and running
I don't know too much about tmux internals but I'm going to take a guess
here:
I think the if-shell command is forking and running asynchronously
and tmux is creating the first window before that command returns and sets
the global option.
Simply setting the option (with -g) does work as expected
Hello there.
I am having issues with the if statements
I have a line in my .tmux.conf like this:
if '[ -n $DISPLAY ]' 'set -g default-terminal screen-256color'
But it only works if I open another window,else the terminal is still
screen..Is there any way to fix this?
---
11 matches
Mail list logo
