X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-5.1 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,URI_HEX X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <1351606847888-94081.post@n5.nabble.com> References: <1351606847888-94081.post@n5.nabble.com> Date: Tue, 30 Oct 2012 12:30:44 -0700 Message-ID: Subject: Re: Command line arguments From: Wynfield Henman To: cygwin@cygwin.com Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Arguments do get passed. So it seems you're doing something wrong. You can't get any sensible answer without showing us exactly what you command line look like. On Tue, Oct 30, 2012 at 7:20 AM, chesschi wrote: > In cygwin, is it possible to pass arguments to a shell script file? I have > installed the latest cygwin with default packages. I found that argument > zero ($0) is correct. However, the number of arguments always returns zero > ($#= 0) and $1, $2... are all null even though I did pass arguments. > > Any idea? Thanks a lot! > > > > -- > View this message in context: http://cygwin.1069669.n5.nabble.com/Command-line-arguments-tp94081.html > Sent from the Cygwin list mailing list archive at Nabble.com. > > -- > 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