Mail Archives: cygwin/2006/05/16/05:09:18
> 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 batchfile has another advantage, when you're not using rxvt but windowsconsole.
Case 1:1) Run the batch file (through the default cygwin shortcut, viaexplorer or whatever) which launches bash in a windows console2) 'exit' the login shellWindow closes. All is fine.
Case 2:1) Run the batch file (through a shortuct, via explorer or whatever)which launches bash in a windows console2) press CTRL-C anytime (shell or not)3) 'exit' the login shellA message pops up: "Terminer le programme de commandes (O/N)?" infrench (translated: "End batch file (Y/N)?"). Signal was not onlyhandled by cygwin, but is also handled by the .bat interpreter, whichinterrupts its execution upon bash return, and ask for interactiveconfirmation. Stupid, as the .bat is at the end anyway (although itmight change its return code). Anyway, that's annoying.
Case 3:1) Run a 'direct' shortcut which launches bash directly(c:\cygwin\bin\bash --login -i), built as it has been suggested and asI did prior to using rxvt or puttycyg.2) press CTRL-C anytime (shell or not)3) 'exit' the login shellWindow closes. All is fine.
Then I switched to rxvt based on this shortcut, and discovered onlyrecently that rxvt pops up a console window and that my shortcutthingie was a heck of a workaround.So I concluded that running .bat files/console was definitely to bepromoted on my list of Most Annoying Things Ever.
Lloeki
- Raw text -