This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Starting mintty via run.exe

I'm trying to create a Windows shortcut which will start mintty indirectly by running a (perl) script which will exec mintty.  I know I can start mintty.exe directly via the shortcut, but the purpose of my script is to wrap the invocation in the proper environment and arguments.  

I'm encountering two problems using run.exe:

1) run.exe doesn't seem to be able to run a hashbang script.  My script starts with #!/usr/bin/perl and runs just fine from a cygwin bash command line, starting a new mintty terminal as expected.  But calling it from run.exe fails.  Clicking on the shortcut flashes some kind of terminal window on the screen, which appears to have no content (but it is hard to tell, since it flashes so quickly) and then the terminal window immediately closes. In this case, my shortcut target is: d:\cygwin\bin\run.exe /path/to/hashbang/script.

2)  When I change my shortcut target to: d:\cygwin\run.exe perl /path/to/hashbang/script, then it runs the script and starts a mintty terminal session, but I still get the flashing terminal window before the eventual mintty starts, which I don't want.  I thought the purpose of run.exe was to hide such a terminal window?  There must be something I'm not understanding about how run.exe works or its purpose.

Finally, is there any way I can debug what's going on without rebuilding run.exe?  For example, can I prevent the flashing window from flashing so quickly (in case there's a message displayed there).


Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]