This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Newbie Questions
- From: Andrey Repin <anrdaemon at yandex dot ru>
- To: Warren Young <warren at etr-usa dot com>, cygwin at cygwin dot com
- Date: Thu, 6 Feb 2014 12:13:52 +0400
- Subject: Re: Newbie Questions
- Authentication-results: sourceware.org; auth=none
- References: <1898639722 dot 6893470 dot 1391541591920 dot JavaMail dot root at ptd dot net> <52F153AE dot 5080704 at gmail dot com> <52F28215 dot 5030801 at ptd dot net> <52F28330 dot 6060101 at cygwin dot com> <52F2AA5D dot 4000000 at etr-usa dot com> <52F2AD84 dot 1050008 at etr-usa dot com> <709102296 dot 20140206020738 at mtu-net dot ru> <52F2D9AF dot 1060409 at etr-usa dot com> <11910654512 dot 20140206050031 at mtu-net dot ru> <52F2E214 dot 1060403 at etr-usa dot com>
- Reply-to: Andrey Repin <cygwin at cygwin dot com>
Greetings, Warren Young!
>> [C:\home\Daemon]$ bash -c ./foo.sh
> That's not the same command I gave you. -c changes how bash.exe
> interprets the following parameter.
According to `man bash', that's the correct command to execute scripts with
bash.
> It matters, because when you right-click a *.sh file in Windows
> Explorer, say Open With, then tell Explorer to use bash.exe to open such
> files now and in the future, it isn't going to stick -c in the command
> for you.
> If you did change the file association in the registry, adding -c, that
> still isn't going to help because Windows Explorer is going to pass the
> full Windows-style path to bash.exe in place of the %1. Plus you still
> have the PATH issues I brought up in my previous email.
--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 06.02.2014, <12:13>
Sorry for my terrible english...
--
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