Re: Starting mintty via run.exe

[Eliot Moss <moss@cs.umass.edu>]

On 10/16/2014 11:51 PM, John Wiersba wrote:

>> So maybe you want: run /bin/bash -c /path/to/hashbang/script
>>
>> This worked for me with a trival mintty-starting hash-bang bash script.

> I found your reply on the mailing list archives and quoted it above.  Yes,
> the same approach worked for me (in my original question I used perl rather
> than bash -c, since my script was written in perl).  That's mainly an
> annoyance that I have to specify the interpreter directly, rather than use
> the shebang line.  But I'm trying to get confirmation that it's not a "bug"
> but rather the way run.exe was designed.

I guess the author will have to confirm, but #! behavior is something built in
to the system calls in Unix, and is likely provided in a little bit different
manner under cygwin.  I am not sure what run.exe would have to do to make it
happen -- maybe add its own functionality to look for and parse a #! line.

> However, do you have any ideas about the flashing window which appears and
> then immediately disappears before the mintty terminal starts?  That's a
> show-stopper.  I thought that was what run.exe was supposed to prevent by
> making that console window hidden?  Do you get the same flashing console
> window with your trivial mintty-starting script?

Sorry, no -- I think I have seen that myself some in the past.  The
author/maintainer of run.exe will probably have to answer these.

By the way, you could create a copy of run.exe called runperl.exe (or maybe
just a link with that name) and it will run perl, as documented in the man
page for run.

Regards -- Eliot

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