Currently, if you call write.table() on a data.frame that includes a POSIXlt or
POSIXct variable, with the default options (space delimited), you won't then be
able to read that file back in using read.table because the POSIXlt and POSIXct
won't get quoted, and they contain a space in them when
On Mon, Mar 21, 2011 at 11:19 PM, Prof Brian Ripley
wrote:
> This is a bug in the package: you are required to quote paths in
> Makefiles, e.g. to allow for spaces in the path.
>
> And let's knock the issue of forward and backwards slashes on the head:
> they are equivalent on Windows. Despite yo
After some offline checks, another workaround is to set LC_COLLATE=C,
and we'll arrange for tools::texi2dvi() to do that.
On Tue, 22 Mar 2011, Tobias Verbeke wrote:
On 03/22/2011 08:41 AM, Martin Maechler wrote:
Tobias Verbeke
on Mon, 21 Mar 2011 23:45:33 +0100 writes:
> L.S. I
On 03/22/2011 08:41 AM, Martin Maechler wrote:
Tobias Verbeke
on Mon, 21 Mar 2011 23:45:33 +0100 writes:
> L.S. I noticed weird tools::texi2dvi behaviour on R-alpha
> when specifying an absolute path to the .tex file.
> The same phenomenon also appears to occur on R-2.1
Thank you,
Ben.
I'm committing the fixes.
Martin
> Ben Bolker
> on Mon, 21 Mar 2011 23:09:29 -0400 writes:
> simplify: logical or character string; should the result
> be simplified to a vector, matrix or higher dimensional
> array if possible? The default, ‘TRUE’, r
> Tobias Verbeke
> on Mon, 21 Mar 2011 23:45:33 +0100 writes:
> L.S. I noticed weird tools::texi2dvi behaviour on R-alpha
> when specifying an absolute path to the .tex file.
> The same phenomenon also appears to occur on R-2.12.2, so
> maybe the issue is independent
