public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu>
To: Bryan VanSchouwen <vanschbm2@gmail.com>, cygwin@cygwin.com
Subject: Re: Problem with output from gawk software in recent Cygwin installation
Date: Mon, 27 Jul 2020 12:51:43 -0400	[thread overview]
Message-ID: <1729e34a-245c-2e87-6604-bebf8e08d62b@cs.umass.edu> (raw)
In-Reply-To: <CAC7Qdh1bPAejJZkV6GY96kcAVKNFDvGcTBpbSfXY6jC-aMGsiQ@mail.gmail.com>

On 7/27/2020 11:47 AM, Bryan VanSchouwen via Cygwin wrote:
> Hello.
> 
> I just tried executing an awk script using the most recent version of gawk,
> but the output did not turn out the way that it was supposed to.
> 
> This script uses the following command to print the output data to the
> output file:
> print(cai[i], rpi[i], i) >
> "Fit_Height_correln_plot_-_cPuMP_vs_2NH2-cPuMP.dat"
> 
> and previously, this command always printed the values of the three
> variables on a single line, separated by spaces; however, now the gawk
> software is automatically adding hard-returns between the values, resulting
> in the three values being printed on separate lines within the data file.
> 
> What is going on here, and how do I permanently make it stop??

Here's a wondering: Could it have to do with line endings?  If Windows
CRLF is getting in there, then the variables might get a CR in them,
which might do weird things.  This assumes those are string variables,
not numeric.

Best - EM

  parent reply	other threads:[~2020-07-27 16:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27 15:47 Bryan VanSchouwen
2020-07-27 16:38 ` Henry S. Thompson
2020-07-27 16:51 ` Eliot Moss [this message]
2020-07-27 17:50   ` Michel LaBarre
2020-07-27 20:17     ` Brian Inglis
     [not found]       ` <CAC7Qdh3AEkbX849S+VyDgSm0_WYRaP5d0zT2QOvmWpd3t3PMkQ@mail.gmail.com>
2020-07-28  4:05         ` Brian Inglis
2020-07-28 15:32           ` Bryan VanSchouwen
2020-07-28 17:08             ` Brian Inglis

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=1729e34a-245c-2e87-6604-bebf8e08d62b@cs.umass.edu \
    --to=moss@cs.umass.edu \
    --cc=cygwin@cygwin.com \
    --cc=vanschbm2@gmail.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).