Re: [Rd] Symlinks when building R on windows

With some additional debug messages in the code, it would seem that when solve.R calls .Internal(La_solve(..)), mod_do_lapack() is called, but PRIMVAL(op) should be 100 for La_solve. Instead, it is 0 and thus La_qr_cmplx is called 2013/12/30 Olivier BARTHELEMY > I tried relaunching the build fo

Re: [Rd] Symlinks when building R on windows

On 14-01-02 6:09 AM, Olivier BARTHELEMY wrote: With some additional debug messages in the code, it would seem that when solve.R calls .Internal(La_solve(..)), mod_do_lapack() is called, but PRIMVAL(op) should be 100 for La_solve. Instead, it is 0 and thus La_qr_cmplx is called That's very stran

[Rd] Sweave trims console output in "tex" mode

Hi In the example .Rnw file below, only the newline between c and d is visible in the resulting .tex file after running R CMD Sweave. What is the reason for this behavior? Newlines are important in LaTeX and should be preserved. In particular, this behavior leads to incorrect LaTeX code gene

Re: [Rd] Sweave trims console output in "tex" mode

On 14-01-02 7:05 PM, Kirill Müller wrote: Hi In the example .Rnw file below, only the newline between c and d is visible in the resulting .tex file after running R CMD Sweave. What is the reason for this behavior? Newlines are important in LaTeX and should be preserved. In particular, this beha

Re: [Rd] Sweave trims console output in "tex" mode

On 01/03/2014 01:45 AM, Duncan Murdoch wrote: You are running with the strip.white option set to TRUE. That strips blank lines at then beginning and end of each output piece. Just set strip.white=FALSE. Thanks, the code below works perfectly. I have also found the documentation in ?RweaveLate

Re: [Rd] Sweave trims console output in "tex" mode

On 14-01-02 7:53 PM, Kirill Müller wrote: On 01/03/2014 01:45 AM, Duncan Murdoch wrote: You are running with the strip.white option set to TRUE. That strips blank lines at then beginning and end of each output piece. Just set strip.white=FALSE. Thanks, the code below works perfectly. I have a

Re: [Rd] Sweave trims console output in "tex" mode

On 01/03/2014 01:59 AM, Duncan Murdoch wrote: But results=tex is not the default. Having defaults for one option depend on the setting for another is confusing, so I think the current setting is appropriate. True. On the other hand, I cannot imagine that "results=tex" is useful at all without

[Rd] class() on substitute(...) output?

Does it make sense to talk about the class of the output of substitute(...)? I'm puzzled by the following outputs: ee <- list( A = substitute( a <- 1 ), B = substitute({ a <- 1 }), C = substitute(( a <- 1 )), D = substitute( a == 1 ) ) > t(sapply(ee, FUN=function(e) { c(typeof=typeof(e),

Re: [Rd] Sweave trims console output in "tex" mode

On 14-01-02 8:04 PM, Kirill Müller wrote: On 01/03/2014 01:59 AM, Duncan Murdoch wrote: But results=tex is not the default. Having defaults for one option depend on the setting for another is confusing, so I think the current setting is appropriate. True. On the other hand, I cannot imagine th

Re: [Rd] class() on substitute(...) output?

I've found 'while', 'for', 'if' and '=' appearing as the "class" of what would ostensibly be "call" objects, as well. (Came across this because I was using S3 dispatch to help do code-walking syntax transformations) I can't find where it is happening in R source, but it seems significant that they

[Rd] Tab formatting in dummy.coef.R

Happy New Year I recognize this is a low priority issue, but... I'll fix it if you let me. There are some TABs where R style calls for 4 spaces. For example R-3.0.2/src/library/stats/R/dummy.coef.R. I never noticed this until today, when I was stranded on a deserted island with only the R source