X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <4786A6B7.40705@upb.de> Date: Fri, 11 Jan 2008 00:13:59 +0100 From: =?ISO-8859-1?Q?Sven_K=F6hler?= User-Agent: Thunderbird 1.5.0.14 (Windows/20071210) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: [BUG?] run.exe and pdflatex References: In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig38FAC80E5A89743B805886C9" X-Virus-Status: Clean Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Note-from-DJ: This may be spam --------------enig38FAC80E5A89743B805886C9 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable > bash -c "exec /bin/echo \$@" some arguments here >=20 > and see what's printed; then read the bash man page for why this happens). Oh, that possibility was new to me. All i wonder, is why the "some" gets lost. Only "arguments here" is printed. And actually i would like to argue, that "$@" instead of $@ should be used. --------------enig38FAC80E5A89743B805886C9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHhqa37Ww7FjRBE4ARAj6GAKDqTlR6kTDq0g+4FLSipbkIPL8YpACgzEgD vPEk5Hg4A8EOQzibph484/c= =snKj -----END PGP SIGNATURE----- --------------enig38FAC80E5A89743B805886C9--