Re: console problem

> i am using intel pentium dual core and windows vista.i tried to > install cygwin.but i installed it only for me(not for all users)..the > problem is when i type crypath or some command in command prompt..but > it says its not recognisedwhen i set path n envt variable ,the > same situation occ

console problem

i am using intel pentium dual core and windows vista.i tried to install cygwin.but i installed it only for me(not for all users)..the problem is when i type crypath or some command in command prompt..but it says its not recognisedwhen i set path n envt variable ,the same situation occurs.i trie

Re: rvxt-20050409-1 console problem [SUMMARY]

Charles Wilson wrote: I'm leaning toward this solution, in a more generic sense, like: "gui-switcher.exe --config=/etc/rxvt-selector.conf" It'll go into the checkX package since it'll leverage a lot of the same code. And that's why I need to track down these issues with rxvt-unicode-X+run+

Re: rvxt-20050409-1 console problem [SUMMARY]

Charles Wilson wrote: (2) add the "smart" hide console code to rxvt-unicode-X and remove the brute-force hide console code. Otherwise, the Igors of the world will have the same "where'd my console go" problem with rxvt-unicode-X. There is a downside to this. As Brian mentioned "run" is not g

RE: rvxt-20050409-1 console problem [SUMMARY]

1. Thanks for taking on the 'rxvt' package. I look forward to the code changes that will make 'man' pages more readable. > >(3) (a) add a command line option to say "force hide console" and use that from scripts > 2. I do not have any need for the script usage that you described so I a

Re: rvxt-20050409-1 console problem

Shouldn't the console-hiding code be unnecessary? Here is a simple approach that I have been using (and have written to this list previously) which makes it possible to start rxvt without resorting to starting a console first: Using a "direct" shortcut instead of shortcutting/running the batch

Re: rvxt-20050409-1 console problem [SUMMARY]

Igor Peshansky wrote: After installing rxvt-20050409-1, starting rxvt from a console bash hides that console. To reproduce: start a console bash, type "rxvt" or "rxvt &" (either way), observe that the bash window goes away (the process is still running, though). I don't think the cygcheck outpu

Re: rvxt-20050409-1 console problem

BTW, isn't is possible to just make the console window created start without SW_VISIBLE? While it would still be created - it would be created invisbly. -cl On Mon, May 15, 2006 at 01:08:07PM -0400, Harig, Mark wrote: > The new console-hiding code causes the console window to be automatically >

RE: rvxt-20050409-1 console problem

-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sven Köhler Sent: Monday, May 15, 2006 12:46 PM To: cygwin@cygwin.com Subject: Re: rvxt-20050409-1 console problem > > You should see it, or perhaps your PC is too fast. > > But prior to the

Re: rvxt-20050409-1 console problem

> Shouldn't the console-hiding code be unnecessary? > > Here is a simple approach that I have been using (and have written > to this list previously) which makes it possible to start rxvt > without resorting to starting a console first: > >1. Using MS Windows Explorer, locate the 'rxvt' binar

RE: rvxt-20050409-1 console problem

mailto:[EMAIL PROTECTED] On Behalf Of Igor Peshansky Sent: Monday, May 15, 2006 10:47 AM To: cygwin@cygwin.com Subject: rvxt-20050409-1 console problem Hi, After installing rxvt-20050409-1, starting rxvt from a console bash hides that console. To reproduce: start a console bash, type "rxvt"

Re: rvxt-20050409-1 console problem

>> $ javaw >> Usage: javaw [-options] class [args...] > > Please re-read what I wrote. What you are seeing here is the expected > result of *not* using a windows console but instead a pty, which to > javaw.exe will appear to be redirection to a pipe. And again, since a > pipe does not involve a

Re: rvxt-20050409-1 console problem

Sven Köhler wrote: > So if there is that nice thing called run, that avoids creating a > console, do we still need the "close the console"-code inside rxvt? Quite the contrary, the console hiding code was just added by Chuck to the recent rxvt refresh so that the extra step of using "run" would n

Re: rvxt-20050409-1 console problem

Sven Köhler wrote: > So how can you explain, that i see text within cygwin, when i run javaw.exe? > > $ javaw > Usage: javaw [-options] class [args...] Please re-read what I wrote. What you are seeing here is the expected result of *not* using a windows console but instead a pty, which to javaw

Re: rvxt-20050409-1 console problem

>> This is not an option in the slightest. A -mwindows application cannot >> interact with the console it was invoked from! That means that all such >> compiled applications would have no I/O when invoked from the command >> line unless redirected to a file. Try compiling "int main() { >> puts("

Re: rvxt-20050409-1 console problem

>> 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". So if there is that nice thing called run, that avoids creating a console, do we still need the "cl

Re: rvxt-20050409-1 console problem

>> So i always was annoyed by the fact, that starting rxvt directly from >> windows opens a console windows. > > Use 'run'. Or, modulo the bug Igor is reporting, the latest refresh of > rxvt. Now i know, what you mean with run! Now i'm satisfied, but ... >> Isn't it possible, to create such an

Re: rvxt-20050409-1 console problem

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 . > >> Isn't it possible, to create such an EXE-

Re: rvxt-20050409-1 console problem

>> 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? >> 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 possibl

Re: rvxt-20050409-1 console problem

Brian Dessent wrote: > This can be set by adding > -Wl,--subsystem,windows (aka -Wl,-mwindows) or -Wl,--subsystem,console > (aka -Wl,-mconsole). Oops, you don't need -Wl with -mwindows / -mconsole is what I was trying to say here, since they are simply shortcuts defined in the specs file that jus

Re: rvxt-20050409-1 console problem

Sven Köhler wrote: > AFAIK, there are EXE-files that open a console, and others, that don't. > > It seems, there is a flag in the EXE-files, which determines if Windows > should open a console or not. It is the "subsystem" flag in the PE header. This can be set by adding -Wl,--subsystem,windows

Re: rvxt-20050409-1 console problem

On Mon, 15 May 2006, Sven Köhler wrote: > > After installing rxvt-20050409-1, starting rxvt from a console bash > > hides that console. To reproduce: start a console bash, type "rxvt" > > or "rxvt &" (either way), observe that the bash window goes away (the > > process is still running, though).

Re: rvxt-20050409-1 console problem

> After installing rxvt-20050409-1, starting rxvt from a console bash hides > that console. To reproduce: start a console bash, type "rxvt" or "rxvt &" > (either way), observe that the bash window goes away (the process is still > running, though). I don't think the cygcheck output is relevant, s

rvxt-20050409-1 console problem

Hi, After installing rxvt-20050409-1, starting rxvt from a console bash hides that console. To reproduce: start a console bash, type "rxvt" or "rxvt &" (either way), observe that the bash window goes away (the process is still running, though). I don't think the cygcheck output is relevant, sinc