X-Spam-Check-By: sourceware.org Message-ID: <454CA10B.7040201@byu.net> Date: Sat, 04 Nov 2006 07:17:47 -0700 From: Eric Blake User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060909 Thunderbird/1.5.0.7 Mnenhy/0.7.4.666 MIME-Version: 1.0 To: cygwin AT cygwin DOT com, goltrock AT wanadoo DOT fr Subject: Re: sh files References: <7064712 DOT post AT talk DOT nabble DOT com> <45451BB0 DOT 5070201 AT byu DOT net> <7174939 DOT post AT talk DOT nabble DOT com> In-Reply-To: <7174939.post@talk.nabble.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Please avoid http://cygwin.com/acronyms/#TOFU - reformatting accordingly. > > Eric Blake-1 wrote: > 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. According to dubcek on 11/4/2006 6:58 AM: > 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. Please don't describe the problem, but show an actual screen capture (copy and paste the text, don't attach a graphical screenshot) of what you typed and what error you got. Saying it doesn't work is useless for us in figuring out why it doesn't work. Showing HOW it doesn't work is MUCH better. > > 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. Indeed. 'cd /cygdrive/c/' is better than 'cd c:/'. > > Can you do anything with that symptom that may also solve the bash problem In bash, ~/ is equivalent to "$HOME/". What is $HOME set to? Try 'echo $HOME', as well as 'printf "$HOME" | od -c', to make sure it has a sane value and that \r hasn't snuck in somewhere. If my original guess is correct, then there is still a possibility that one of your startup scripts has CRLF line endings, lives on a binary mount, and assigns the variable HOME. The default /etc/profile installed by cygwin does not change the value of HOME, but perhaps you have installed one of your own startup scripts that does so. You can use 'bash -vxli' to see a verbose listing of everything bash does at startup, to try and figure out where HOME is being reset. But until you follow directions: > Problem reports: http://cygwin.com/problems.html and include 'cygcheck -svr' output as an attachment, these are only guesses. - -- Life is short - so eat dessert first! Eric Blake ebb9 AT byu DOT net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFTKEL84KuGfSFAYARAn70AKDGp289B/sBouRJSToVbsoMwuj3agCgw0E0 DD1SkwRTONHDkGapnxeXe18= =B5Ex -----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/