On Fri, Aug 14, 2009 at 05:29:04PM +0200, Corinna Vinschen wrote: >On Aug 14 11:19, Christopher Faylor wrote: >> On Fri, Aug 14, 2009 at 04:44:42PM +0200, Corinna Vinschen wrote: >> >On Aug 14 10:15, Charles Wilson wrote: >> >> Later, when W7 in is more widespread use (e.g. when I have personal >> >> access to it), I'll see if I can improve the situation a bit. Maybe I'll >> >> add a switch "-f/--flicker-ok" to enable use of a mechanism similar to >> >> urxvt[d]-X's hide_console() [only, without the 'check to see if this >> >> console already existed before I was launched' intelligence] rather than >> >> cygwin's CREATE_NO_WINDOW, just for situations like urxvt[d]-X and Ken's >> >> emacs example. >> > >> >I just tested this further. If you omit the CREATE_NO_WINDOW flag >> >to CreateProcess, the console window still flickers when starting >> >urxvt, but the CPU usage does not stick to 100%. Since XWin and >> >xterm are apparently unaffected by this (no flickering cmd window) >> >it looks like that's the better interim solution. >> >> Isn't just creating the process with SW_HIDE good enough? > >run uses the SW_HIDE flag in CreateProcess, but for some reason >it doesn't help for urxvt.
I know I should be downloading sources and inspecting things rather than making obvious suggestions but I don't suppose that urxvt calls FreeConsole? cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
