public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Warren Young <warren@etr-usa.com>
To: Cygwin-L <cygwin@cygwin.com>
Subject: Re: What does Dos mode vs unix mode mean when you install cygwin
Date: Tue, 17 Jul 2001 12:01:00 -0000	[thread overview]
Message-ID: <3B548B79.50C9C09E@etr-usa.com> (raw)
In-Reply-To: <EF45EA07AEA2D2118E920008C7B14102066B2B88@mvex02.mv.intuit.com>

"Castle, Eric" wrote:
> 
> just how cygwin, including processing files in perl, uses either \r\n or \n
> for line termination?

Yes, and how text files are created, by default.

> I don't recall the old installer program (called full.exe) ask that question
> back on B18.

It's a fairly new feature.

> Any recomendation on which type to use? I've been choosing "dos" but not
> sure what that is really doing vs choosing unix.

I've had perl scripts copied over from the Linux box break because I was
using chop() to get rid of line endings instead of chomp().  If you tell
Cygwin to expect Unix line endings, that problem doesn't occur, but
then, maybe you have a lot of DOS text files already.  If I try to use
Cygwin on my Visual C++ source files, for example, I need to be using
DOS text mode.

That's why you're given a choice -- one answer isn't right for everyone.

Hmmm, an *ix lover at Intuit...so when's Quicken for Linux coming out? 
:)
-- 
= Warren -- ICBM Address: 36.8274040 N, 108.0204086 W, alt. 1714m

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

      parent reply	other threads:[~2001-07-17 12:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-16 17:16 Castle, Eric
2001-07-16 20:41 ` Tim Prince
2001-07-17  1:37   ` Corinna Vinschen
2001-07-17  4:08   ` Help required with man Dave BT
2001-07-17 12:01 ` Warren Young [this message]

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=3B548B79.50C9C09E@etr-usa.com \
    --to=warren@etr-usa.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).