X-Spam-Check-By: sourceware.org
Message-ID: <7174939.post@talk.nabble.com>
Date: Sat, 4 Nov 2006 05:58:54 -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


Hi Eric,
Here I am again. None of the answers that I received to my query were
helpful. 
However, suddenly I thought that I did not mention one symptom which may be
related to my problem and which might help solve the problem.
In my previoius cygwin version where everything worked perfectly, whenever I
wanted to have access to a file, I could use the command:

cd ~/ followed by the path where the file was loicated.

But in the new cygwin version, the machine does not recognize the ~
directory. So, instead I know write the
cd c:/ followed by the path ...
(That works). But that is not the way it should be.

Can you do anything with that symptom that may also solve the bash 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#a7174939
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/