Hello,
I switched from the tabbed extensions to my WM tabs recently.
(I now think it's up to the WM and I'm also considering this
for the browser)
I used to have some bugs with the perl extension and missing features
(easy switching, attach/detach, mouse focus for dead-keys, ...)
Anyway there is one side where the tabbed extensions miss me :
the "window activity" is a really nice feature.
I would like to share so thoughts about that,
To resolve that, first "urgentBell: true",
then I used the attached perl extension:
on_add_lines { $term->scr_bell if ! $term->focus &&
$term->resource("visualBell"); }
First problem I may need to desactivate it sometimes when, eg, a compilation
happens, or when I'm on another desktop, I still have to solve that
by using a key binding in the extension to {de,re}activate.
But here comes the question, I make some tests about performances (quite
afraid about the on_add_lines hook) but I wasn't able to get any stable
results between xterm, urxvt-tabbed, urxvt-notifiy display /dev/urandom or
hex /dev/zero. Doesn't such hooks need to be conditionally unhooked at
runtime (I don't know perl enough and it's maybe totally ingenuous),
when eg, term has focus ?
I would also like a $term->scr_is_ringing so I can add it to the condition
and not ring the bell again and again.
I experience another problem : resizing a window make all tabs being rewritten
so all terminals blink asking attention (urxvt-tabbed avoided that)
Another question is on_add_lines brings a lot of granularity but shouldn't it
called on_add_char and a new on_add_newline created (I'm just curious about
performance if lines are filtered at C level even if I'm still not able to find
a good test case)
Any thoughts ?
Raph
_______________________________________________
rxvt-unicode mailing list
[email protected]
http://lists.schmorp.de/cgi-bin/mailman/listinfo/rxvt-unicode
