Hi Joshua,
Thank you for the input!
I agree that it is non-trivial to solve the cases you & I have posed.
However, I would wholeheartedly support having an error spit back for any
function that does not explicitly support a class. In this case, if I
attempt to do sapply(x, class), and
On Wed, Nov 2, 2011 at 7:40 PM, Henrik Bengtsson wrote:
> I'd like to be able to change some default settings only in the case
> when checking a package with 'R CMD check'. More precisely, I'd like
> to execute a piece of R code before the Rd examples and/or test
> scripts are evaluated by 'R CMD
> I agree that it is non-trivial to solve the cases you & I have posed.
> However, I would wholeheartedly support having an error spit back for any
> function that does not explicitly support a class. In this case, if I
> attempt to do sapply(x, class), and 'x' is of class "difftime", then I
Mike,
On time classes specifically, the lubridate package
with documentation
Garrett Grolemund, Hadley Wickham (2011).
Dates and Times Made Easy with lubridate.
Journal of Statistical Software, 40(3), 1-25.
http://www.jstatsoft.org/v40/i03/.
solves many confusion problems. Does it handle the
Hi,
just saw "require vignettes to declare their encoding (trunk@57560)". Having
played with non-ascii vignettes (well, a lot of Chinese...) on-and-off for
almost two weeks, I noticed it was a bit odd that a *commented*
\usepackage[utf8]{inputenc} had any effort at all on R's Sweave behavior -
Hi everyone,
I was trying to reproduce building a 32 bit version of R on a 64 bit
Ubuntu 11.04 machine (which worked before) with the latest version of
R in SVN but am getting this error:
make[3]: Leaving directory `/home/vinh/Downloads/R/trunk/src/modules/lapack'
/usr/bin/ld: skipping incompatib
On 03/11/2011 10:49 AM, Renaud Gaujoux wrote:
On 03/11/2011 16:28, Duncan Murdoch wrote:
> On 03/11/2011 10:21 AM, Renaud Gaujoux wrote:
>> Thank you Georgi.
>> With the fix \long the output is indeed consistent with the
>> documentation.
>> I think my use of cat() worked by luck as its outp
On 03/11/2011 16:33, Georgi Boshnakov wrote:
Dear Renalud,,
Would a 'results=tex' (html, text) be possible? or 'results=source' that
could be combined with \if{format}{text}?
This may well be a clean approach.
After my previous email, I looked again at the definition of thr \AsIs macro.
Its
On 03/11/2011 16:28, Duncan Murdoch wrote:
On 03/11/2011 10:21 AM, Renaud Gaujoux wrote:
Thank you Georgi.
With the fix \long the output is indeed consistent with the
documentation.
I think my use of cat() worked by luck as its output should not have
been rendered.
Would a 'results=tex' (htm
Dear Renalud,,
> Would a 'results=tex' (html, text) be possible? or 'results=source' that
> could be combined with \if{format}{text}?
This may well be a clean approach.
After my previous email, I looked again at the definition of thr \AsIs macro.
Its purpose seems to be to typeset text contai
On 3 November 2011 at 08:54, William Revelle wrote:
| Dear R developers,
|
| Is there a way to pretest a package on the Solaris-sparc and solaris-x86
systems equivalent to the win-builder check?
Nope, not as far as I know. For Rcpp we are very much in the same boot.
There was word of an upc
On 03/11/2011 10:21 AM, Renaud Gaujoux wrote:
Thank you Georgi.
With the fix \long the output is indeed consistent with the documentation.
I think my use of cat() worked by luck as its output should not have
been rendered.
Would a 'results=tex' (html, text) be possible? or 'results=source' that
Thank you Georgi.
With the fix \long the output is indeed consistent with the documentation.
I think my use of cat() worked by luck as its output should not have
been rendered.
Would a 'results=tex' (html, text) be possible? or 'results=source' that
could be combined with \if{format}{text}?
Th
Dear R developers,
Is there a way to pretest a package on the Solaris-sparc and solaris-x86
systems equivalent to the win-builder check?
My psych package (1.1.10 and 1.1.11) passes all checks for the Mac on my
system, on the win-builder checking system supported by Uwe, and then passes
Kurt's
Dear Duncan and Renauld,
The error caused by the empty line(s) can be removed by prefixin the macro with
\long
in Rd.sty:
\long\def\Rd@AsIsX#1{\normalfont #1\egroup}
but the slash-n's come up in the output.
In "text mode" this seems not to be a problem. Following normal TeX rules one
needs
Although I use Latex quite a lot, I am not literate in Latex macro
languages (e.g. the definition of AsIs).
Is there (I am sure there is) a reason why a plain verbatim environment
is not used in this case?
On 03/11/2011 14:19, Duncan Murdoch wrote:
On 11-11-03 7:58 AM, Renaud Gaujoux wrote:
On 11-11-03 7:58 AM, Renaud Gaujoux wrote:
Georgi, I tried with paste() instead of cat(), but I then get the
following in my PDF manual:
[1] "line\nnext line"
i.e. what would be printed in the R console, which is not what I want.
I would like to get something like this in the Latex code:
\begi
Georgi, I tried with paste() instead of cat(), but I then get the
following in my PDF manual:
[1] "line\nnext line"
i.e. what would be printed in the R console, which is not what I want.
I would like to get something like this in the Latex code:
\begin{verbatim}
line
next line
\end{verbatim}
18 matches
Mail list logo
