X-Spam-Check-By: sourceware.org Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: updated bash to latest 3.1.17(8)-release; startup has errors now Date: Tue, 3 Oct 2006 17:13:50 -0400 Message-ID: <31DDB7BE4BF41D4888D41709C476B657041690F7@NIHCESMLBX5.nih.gov> In-Reply-To: <45226750.9090909@cygwin.com> From: "Buchbinder, Barry \(NIH/NIAID\) [E]" To: X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k93LE10N031807 Larry Hall (Cygwin) wrote: > On 10/03/2006, DePriest, Jason R. wrote: > > > >> vi did not show any unusual line endings (CR/LF) in /etc/profile >> before I sent my message in > > vi/vim will only show you the CR/LF if you tell it to. So if you're > not looking for them, vi/vim may have hidden them from you. You may > want to try 'od -c' on the file(s) in question. Even if it does not show you the CR at the end of the line, vim will tell you if it thinks that it's opening a DOS file, but you have to look at the status line at the bottom before doing anything. Here's an example: "evim.bat" [dos] 47L, 977C -- 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/