X-Spam-Check-By: sourceware.org
Message-ID: <7080971.post@talk.nabble.com>
Date: Mon, 30 Oct 2006 11:15:31 -0800 (PST)
From: dubcek <goltrock AT wanadoo DOT fr>
To: cygwin AT cygwin DOT com
Subject: Re: sh files
In-Reply-To: <45451BB0.5070201@byu.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: goltrock AT wanadoo DOT fr
References: <7064712 DOT post AT talk DOT nabble DOT com> <45451BB0 DOT 5070201 AT byu DOT net>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com


Thanks Eric. Unfortunately, your remedy did not work. As I mentioned in my
original mail, all my .sh files were made under unix. But I tried d2u anyway
(you never know), but I got the same result.

Here is an example of one of my unsophisticated .sh files; it was intended
to clean up after a latex session:
rm *.div *.aux *.log 

when I run the clean.sh (this was the name I gave to it), I get the 'command
not found' error reply.

Does that help to make you better see my problem?
Thanks.
dubcek


Eric Blake-1 wrote:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> According to dubcek on 10/29/2006 12:59 PM:
>>>From the time I started using UNIX, I have made at least a hundred
different
>> .sh files, all of which ran perfectly on my first version of cygwin. But
>> they don't work on the new version.
> 
> What are the failure symptoms?  Without any further details, my guess is
> that you have CRLF line endings, but a binary mount.  Use the d2u program
> to convert your .sh files to plain LF line endings, and things should
> clear up.
> 
> http://cygwin.com/ml/cygwin-announce/2006-10/msg00026.html
> 
> - --
> Life is short - so eat dessert first!
> 
> Eric Blake             ebb9 AT byu DOT net
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2.1 (Cygwin)
> Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQFFRRuv84KuGfSFAYARAtdiAJ96mdxigxSrCNJGikpv1N/SBiLfvQCaAmRe
> z/b+ZVxXhG7ONhtnyPRrnsI=
> =HRc0
> -----END PGP SIGNATURE-----
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:       http://cygwin.com/problems.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/sh-files-tf2535809.html#a7080971
Sent from the Cygwin Users mailing list archive at Nabble.com.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/