monitor-content matches

2010-05-30 Thread clemens fischer
'uname -rims' -> Linux 2.6.33.4-spott i686 AuthenticAMD
tmux-CVS from today

Hi,

I have these settings in ".tmux.conf":

set-window-option -g monitor-content '[0-9]* [0-9]* [#$] ?'
set-option -g visual-content on

designed to match my shells prompt[1] looking like this:  "0 4 # ".  The
first number is the exit status of the last command, then comes the PTY
number and then "#" for root and "$" for a regular user, a space and
there's the bash waiting for input.

Tmux flags content as soon as anything is printed to screen, not only
this prompt.  Linux has fnmatch(3), I see it is used without any flags
every place, shouldn't it match _new_ content only?  In
"window.c::window_pane_search()" it is used on every line on the screen
(without history, it seems).  But why doesn't it trigger as soon as any
prompt is seen, ie.  immediately?

[1]
1 4 # echo "${PS1}"
\w\n${_last_status} ${_this_pty} \$


clemens


--

___
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users


Re: fatal: main: msgbuf_write failed

2010-05-30 Thread clemens fischer
On Fri-2010/04/23-19:45 chr wrote:

> I suspect that is some permissions problem. If I chmod 777
> the socket directory (previously 700), I get:
> 
> $ tmux
> can't create socket: Permission denied

Did you do "chmod 777 ..." or "chmod 0777 ..."?  The former would be
interpreted in decimal, the latter is the octal you want.  You could
also try the symbolic mode "chmod ug=rwxt ...".

777 decimal is 1411 octal, meaning u=r,g=x,o=xt AFAIK.


clemens


--

___
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users


Re: fatal: main: msgbuf_write failed

2010-05-30 Thread Nicholas Marriott
On Sun, May 30, 2010 at 06:05:25PM +0200, clemens fischer wrote:
> On Fri-2010/04/23-19:45 chr wrote:
> 
> > I suspect that is some permissions problem. If I chmod 777
> > the socket directory (previously 700), I get:
> > 
> > $ tmux
> > can't create socket: Permission denied
> 
> Did you do "chmod 777 ..." or "chmod 0777 ..."?  The former would be
> interpreted in decimal, the latter is the octal you want.  You could

chmod is not as dumb as that.

$ touch x && chmod 777 x && ls -l x
-rwxrwxrwx  1 nicholas  nicholas 0B May 30 17:33 x*

> also try the symbolic mode "chmod ug=rwxt ...".
> 
> 777 decimal is 1411 octal, meaning u=r,g=x,o=xt AFAIK.
> 
> 
> clemens
> 
> 
> --
> 
> ___
> tmux-users mailing list
> tmux-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/tmux-users

--

___
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users


Re: fatal: main: msgbuf_write failed

2010-05-30 Thread clemens fischer
Nicholas Marriott wrote:

> On Sun, May 30, 2010 at 06:05:25PM +0200, clemens fischer wrote:
>
>> Did you do "chmod 777 ..." or "chmod 0777 ..."? The former would be
>> interpreted in decimal, the latter is the octal you want.  You could
> 
> chmod is not as dumb as that.
> 
> $ touch x && chmod 777 x && ls -l x
> -rwxrwxrwx  1 nicholas  nicholas 0B May 30 17:33 x*

Well, I figured he 1) might use a shell mucking with numbers and 2) use
the chmod(1) from netbsd.  Over the years working with freebsd,
I experienced significant differences between the various
implementations.

It was a wild shot, but if it had helped, well, it had helped.


clemens


--

___
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users


Re: monitor-content matches

2010-05-30 Thread Nicholas Marriott
It only scans when new content appears but it scans the whole window,
not just what was added.

Not ideal but that's the way it works right now.


On Sun, May 30, 2010 at 05:16:06PM +0200, clemens fischer wrote:
> 'uname -rims' -> Linux 2.6.33.4-spott i686 AuthenticAMD
> tmux-CVS from today
> 
> Hi,
> 
> I have these settings in ".tmux.conf":
> 
> set-window-option -g monitor-content '[0-9]* [0-9]* [#$] ?'
> set-option -g visual-content on
> 
> designed to match my shells prompt[1] looking like this:  "0 4 # ".  The
> first number is the exit status of the last command, then comes the PTY
> number and then "#" for root and "$" for a regular user, a space and
> there's the bash waiting for input.
> 
> Tmux flags content as soon as anything is printed to screen, not only
> this prompt.  Linux has fnmatch(3), I see it is used without any flags
> every place, shouldn't it match _new_ content only?  In
> "window.c::window_pane_search()" it is used on every line on the screen
> (without history, it seems).  But why doesn't it trigger as soon as any
> prompt is seen, ie.  immediately?
> 
> [1]
> 1 4 # echo "${PS1}"
> \w\n${_last_status} ${_this_pty} \$
> 
> 
> clemens
> 
> 
> --
> 
> ___
> tmux-users mailing list
> tmux-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/tmux-users

--

___
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users