Eliot, I'm sorry for double posting. I subscribed this morning, sent back the confirmation email, posted my question and...didn't hear anything. I never got my original question from the list nor your reply. Not in my inbox nor in my spam folder. I figured that my question must have somehow been discarded because I wasn't registered on the list yet.
After an hour or two, I tried resubscribing to the list (I was already subscribed) and then reposted my question. I did later see an announcement from Corinna, a post from Ken Brown about emacs and ispell, an announcement from Jon Turney, a post from Christian Franke about exec and PATH, and finally another emacs post from Ken Brown. I will check the list archives for your reply, since I still don't know what it is. Thanks in advance for your reply. -- John ----- Original Message ----- > From: Eliot Moss <m...@cs.umass.edu> > To: cygwin@cygwin.com > Cc: jrw32...@yahoo.com > Sent: Thursday, October 16, 2014 7:34 PM > Subject: Re: Starting mintty via run.exe > > On 10/16/2014 3:43 PM, John Wiersba wrote: > >> 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). > > You posted this same question this morning ... > > And I answered it about 20 minutes later. > > Why are you posting again? You risk annoying the > list subscribers ... > > Regards -- Eliot Moss > > -- > 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 > -- 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
