public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Nellis, Kenneth (Conduent)" <Kenneth.Nellis@conduent.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: cygcheck (64&32) output contains DOS line terminators
Date: Tue, 17 Jan 2017 21:45:00 -0000	[thread overview]
Message-ID: <0D835E9B9CD07F40A48423F80D3B5A704BBDBF0F@USA7109MB022.na.xerox.net> (raw)
In-Reply-To: <82bffdef-29c2-f9cb-4382-b01d8f7e6e69@SystematicSw.ab.ca>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 943 bytes --]

From: Brian Inglis 
> On 2017-01-17 13:21, Marco Atzeri wrote:
> > On 17/01/2017 21:00, Brian Inglis wrote:
> >> All cygcheck output seems to have DOS line terminators in both
> >> Cygwin 64 & 32.
> >> Is this by design or just because it's a native Windows app?
> > second one
> 
> So by accident rather than intent?
> Could that be easily changed to be more Cygwin-like?
> Or would it involve more difficult changes to a lower level API?
> 
> >> It's annoying in command lines and scripts to have to strip the \r.

I agree. Despite the fact that it's a "Windows app", the fact remains
that it is installed in /usr/bin, so its clear intent is to be run
from the Cygwin command line.  --Ken Nellis
\0ТÒÐÐ¥\a&ö&ÆVÒ\a&W\x06÷'G3¢\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒ÷\a&ö&ÆV×2æ‡FÖÀФd\x15\x13¢\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöf\x17\x12ðФFö7VÖVçF\x17F–öã¢\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöFö72æ‡FÖÀÐ¥Vç7V'67&–&R\x06–æfó¢\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöÖÂò7Vç7V'67&–&R×6–×\x06ÆPРÐ

  reply	other threads:[~2017-01-17 21:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-17 20:00 Brian Inglis
2017-01-17 20:22 ` Marco Atzeri
2017-01-17 20:52   ` Brian Inglis
2017-01-17 21:45     ` Nellis, Kenneth (Conduent) [this message]
2017-01-17 23:43       ` cyg Simple

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=0D835E9B9CD07F40A48423F80D3B5A704BBDBF0F@USA7109MB022.na.xerox.net \
    --to=kenneth.nellis@conduent.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).