public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: Starting mintty via run.exe
Date: Thu, 16 Oct 2014 15:05:00 -0000	[thread overview]
Message-ID: <543FDEB6.7060302@cs.umass.edu> (raw)
In-Reply-To: <1413470693.33063.YahooMailNeo@web162805.mail.bf1.yahoo.com>

On 10/16/2014 10:44 AM, John Wiersba wrote:
> I'm trying to create a windows shortcut which will start mintty indirectlyby 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.  It 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.

I think it may be designed to deal only with actual executables (.exe files).
The wording of the man page is ambiguous, but suggestive of this in that it
speaks of "Windows programs".

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.

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

  reply	other threads:[~2014-10-16 15:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-16 14:44 John Wiersba
2014-10-16 15:05 ` Eliot Moss [this message]
2014-10-16 19:43 John Wiersba
2014-10-16 23:34 ` Eliot Moss
2014-10-17  3:39   ` John Wiersba
2014-10-17  3:51     ` John Wiersba
2014-10-17 13:14       ` Eliot Moss

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=543FDEB6.7060302@cs.umass.edu \
    --to=moss@cs.umass.edu \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).