public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: arnold@skeeve.com
To: cygwin@cygwin.com, arnold@skeeve.com
Subject: Re: [bug-gawk] gawk Regression: CR characters are not stripped on Windows
Date: Tue, 06 Mar 2018 04:42:00 -0000	[thread overview]
Message-ID: <201803060358.w263wSEL001406@freefriends.org> (raw)
In-Reply-To: <5310615097.20180305235805@yandex.ru>

Andrey Repin <anrdaemon@yandex.ru> wrote:

> Greetings, arnold@skeeve.com!
>
> > Corinna Vinschen <corinna-cygwin@cygwin.com> wrote:
>
> >> Hi Arnold,
> >>
> >> On Mar  5 06:36, arnold@skeeve.com wrote:
> >> > Is there a way to distinguish cygwin from msys at compile time?
> >> > I would not object to restoring the behavior for msys only.
> >>
> >> __MSYS__ vs. __CYGWIN__
> >>
> >>
> >> Corinna
>
> > Excellent. I will probably do that, soon.
>
> Keep in mind that you should avoid relying on __CYGWIN__ if possible.
> Only if certain POSIX mandated functionality could not be implemented at all
> using WinAPI you may go for this macro to work around compatibility issues.

I don't think it's a problem; I am testing for MSYS.  The change
is now in git in posix/gawkmisc.c.

Thanks,

Arnold

--
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

      parent reply	other threads:[~2018-03-06  4:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-27  7:22 Orgad Shaneh
2018-02-27  9:50 ` Andrey Repin
2018-02-27 10:13   ` Orgad Shaneh
2018-02-27 12:55     ` Steven Penny
2018-02-27 11:09 ` Houder
2018-02-27 15:03 ` Brian Inglis
2018-02-27 16:56 ` Eric Blake
2018-03-05 13:36 ` [bug-gawk] " arnold
2018-03-05 14:00   ` Corinna Vinschen
2018-03-05 14:23     ` arnold
2018-03-05 14:43       ` arnold
2018-03-05 21:54       ` Andrey Repin
2018-03-06  0:33         ` Vince Rice
2018-03-06  4:42         ` arnold [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=201803060358.w263wSEL001406@freefriends.org \
    --to=arnold@skeeve.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).