public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: dircolors generates output with '\r\n' ?
Date: Thu, 30 Jan 2014 18:21:00 -0000	[thread overview]
Message-ID: <52EA9807.5060302@cygwin.com> (raw)
In-Reply-To: <5F8AAC04F9616747BC4CC0E803D5907D0C47638A@MLBXv04.nih.gov>

On 1/30/2014 12:04 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
> Hi,
>
> I was trying to use the dircolor command on CYGWIN, and it did not work because
> the two lines, which this command produces are separated by CRLF (which when
> sourced by bash are not understood, bash seems to expect single LFs):
>
> LS_OPTIONS='...';\r\n
> export LS_OPTIONS\r\n
>
> Why there are Windows-style EOLs in there?

If you edit the file with a native Windows editor, it will typically
introduce the Windows-style EOL characters.  Use 'dos2unix' or your
favorite utility to clean that up.


-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

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

  reply	other threads:[~2014-01-30 18:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-30 17:05 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2014-01-30 18:21 ` Larry Hall (Cygwin) [this message]
2014-01-30 18:31   ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2014-01-30 18:38     ` Larry Hall (Cygwin)
2014-01-30 18:59       ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52EA9807.5060302@cygwin.com \
    --to=reply-to-list-only-lh@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).