Marc Lehmann a écrit : > On Tue, Apr 27, 2010 at 07:35:30PM +0200, giggz <[email protected]> wrote: >> I have an eeepc with debian stable. I'm using urxvt. On eeepc we have to >> care of the power consumption. so I have started powertop under root in >> my urxvt. Surprisingly urxvtd is the programm which does the mode wake >> up. > > Obviously, if you run powertop inside urxvt, it will wake urxvt up when it > does output (and so does any other terminal). > > In addition, urxvt will wake up at least once/minute (libev timejump > detection). > > Otherwise, urxvt (and urxvtd) only wake up when there is an external > event, or you use something else that wakes up (for example, for the > blinking cursor, urxvt has to wake up regularly) - there are no unnecessary > wakeups with (standard) urxvt. > > If you have too many wake-ups, make sure nothing else wakes up urxvt (e.g. > some kind of clipboard program), and you don't use anything that obviously > involves a timer (such as a blinking cursor). > > Anything else stands in direct relation to user events (clicking, focus > changes, selection and so on). > >> With lxterminal I don't have this behaviour. > > Maybe you should explain your behaviour in more detail. >
ok : I just run powertop in urxvt and in the report of powertop, urxvt is always first (20% of the wake up). In order to compare I run powertop in lxterminal and lxterminal doesn't appear at all. That's what I observe. But you solve the problem. With URxvt*cursorBlink: False urxvt doesn't appear anymore. Thx Best regards, Guillaume _______________________________________________ rxvt-unicode mailing list [email protected] http://lists.schmorp.de/cgi-bin/mailman/listinfo/rxvt-unicode
