From: Michael Hannon <firstname.lastname@example.org>
To: "Thomas S. Dye" <email@example.com>, Eric Schulte <firstname.lastname@example.org>
Cc: Org-Mode List <email@example.com>
Subject: Re: Babel: communicating irregular data to R source-code block
Date: Tue, 24 Apr 2012 00:07:09 -0700 (PDT) [thread overview]
Message-ID: <1335251229.83988.YahooMailNeo@web161905.mail.bf1.yahoo.com> (raw)
On Monday, April 23, 2012 at 11:44 PM Thomas S. Dye wrote:
> The documentation of read.table has this:
> The number of data columns is determined by looking at the first five lines
> of input (or the whole file if it has less than five lines), or from the
> length of col.names if it is specified and is longer. This could conceivably
> be wrong if fill or blank.lines.skip are true, so specify col.names if
> necessary (as in the ‘Examples’).
> The example is this:
> read.csv(tf, fill = TRUE, header = FALSE,
> col.names = paste("V", seq_len(ncol), sep = ""))
> where read.csv is a synonym of read.table with preset arguments.
> This explains why the sixth line wraps.
Thanks, Tom. I had just run across this myself. I guess I need to walk a mile
in somebody's moccasins before complaining, but this behavior on the part of R
seems totally stupid to me.
I'm going to have to mull this over some more.
next prev parent reply other threads:[~2012-04-24 7:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-21 20:17 Babel: communicating irregular data to R source-code block Michael Hannon
2012-04-22 0:44 ` Thomas S. Dye
2012-04-22 15:58 ` Eric Schulte
2012-04-23 16:46 ` Thomas S. Dye
2012-04-23 15:41 ` Eric Schulte
2012-04-23 19:17 ` Thomas S. Dye
2012-04-23 22:24 ` Michael Hannon
2012-04-23 21:05 ` Eric Schulte
2012-04-24 0:23 ` Thomas S. Dye
2012-04-23 22:55 ` Eric Schulte
2012-04-24 6:44 ` Thomas S. Dye
2012-04-24 7:07 ` Michael Hannon [this message]
2012-04-24 17:18 ` Thomas S. Dye
2012-04-24 19:23 ` Thomas S. Dye
2012-04-25 23:52 ` Thomas S. Dye
2012-04-26 2:06 ` Michael Hannon
2012-04-26 6:34 ` Thomas S. Dye
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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).