Calling Cygwin to start a shellscript

Alexey Borzenkov
Sat May 16 07:25:00 GMT 2009

On Sat, May 16, 2009 at 2:51 AM, Brian Mathis <> wrote:
> What I have done is associate files with a .sh extension to run the
> bash.exe file.  Works for me, but I'm not sure if it pulls in all the
> environment variables - but I don't need them.

If you ever need those environment variables, take a look at my (though there's no
documentation at the moment, I hope people would understand it on
their own). In short, you create C:\cygwin\bin-public directory, where
tiny executable proxies are generated for any command you like (like
bash, git, ruby, etc.) and a configuration file that describes
environment changes. You can add bin-public to your path, it's almost
as fast as executing the command directly from bin (my primary reason
for creating shell-wrapper was extremely long time it took to bash
--login), and there are no commands in your path that you don't need
(or that might clash with something else).

I also usually create a cygwin.exe wrapper (it's all in the batch
file), which allows me to type "cygwin command [parameters]" directly
from FAR Manager/cmd prompt...

Unsubscribe info:
Problem reports:

More information about the Cygwin mailing list