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
