On Mon, 15 May 2006, Sven Köhler wrote: > >> So i always was annoyed by the fact, that starting rxvt directly from > >> windows opens a console windows. > > > > Hence the recommended use of "run". > > run?
Yes, see <http://cygwin.com/packages/run/>. > >> Isn't it possible, to create such an EXE-file, that doesn't open a > >> console? Would that cause any problems with cygwin? > > > > It's possible. But one (important) side effect is that window-mode > > applications cannot write to a console. So, "rxvt --help" would be > > useless if rxvt were to be made a window-mode app. > > Oops, yes. > > Hmm ... but ... > > Would "rxvt.exe --help" work, if you run in from a cygwin-shell? > wouldn't that be sufficient? Which Cygwin shell? It won't work from a console bash. > Something that i just noticed: do you have java installed? there is that > javaw.exe-thing. It's such a window-mode application. And if i run > "javaw" inside cygwin, then it prints a help-screen to the console! No, it doesn't, unless you run it from rxvt, xterm, or bash with CYGWIN=tty (in which case, as far as that app is concerned, the output is redirected to a file -- as Brian already mentioned). > >> That would make any "hide the console"-code unnecessary. > > If there is some other possibility, to hide the console, (what is that > "run" command that you mean?), then i would remove the "hide the > console"-code. > > There are only two things, that i'd like to be abled to do: > a) start rxvt.exe directly from windows without a console-windows > b) run it from inside cygwin like any other app Use "run". > >> P.S.: i can reproduce the bug too. > > > > Note that my issue is actually the opposite: I start rxvt from an > > unrelated console, and I *want* that console to stay visible. Looks > > like the new console-hiding code is a bit over-eager... If I have the > > time, I'll take a look at the changes to see if there's a simple fix. > > Yes, i know. But i thought, that a window-mode application _could_ be a > more clean sollution to the problem, because the "close the > console"-code (which is a workaround IMHO) could be removed. But at the cost of losing console output -- which is not an option. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ [EMAIL PROTECTED] | [EMAIL PROTECTED] ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte." "But no -- you are no fool; you call yourself a fool, there's proof enough in that!" -- Rostand, "Cyrano de Bergerac"
-- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
