A follow up on the actions taken.
1) In R >= 2.7.0 whether Sweave() inserts
\usepackage{/full/path/to/Sweave}
is controlled by the environment variable SWEAVE_STYLEPATH_DEFAULT which
sets the default for RweaveLatex's 'stylepath' argument. So setting
SWEAVE_STYLEPATH_DEFAULT=FALSE inserts jus
On Thu, 10 Apr 2008, Kurt Hornik wrote:
>> Prof Brian Ripley writes:
>
>> I suggest that we try to program a solution in Sweave. It only inserts
>> the path to the file is stylepath=TRUE in RweaveLatexSetup, so it seems
>> to be that
>
>> Sweave(stylepath=FALSE)
>
>> is all that is needed. T
> Prof Brian Ripley writes:
> I suggest that we try to program a solution in Sweave. It only inserts
> the path to the file is stylepath=TRUE in RweaveLatexSetup, so it seems
> to be that
> Sweave(stylepath=FALSE)
> is all that is needed. That seems to work, although of course obliges
>
I suggest that we try to program a solution in Sweave. It only inserts
the path to the file is stylepath=TRUE in RweaveLatexSetup, so it seems
to be that
Sweave(stylepath=FALSE)
is all that is needed. That seems to work, although of course obliges
people to make sure Sweave.sty is in their l
On 4/10/2008 1:18 PM, Patrick Aboyoun wrote:
> Thanks Duncan,
> I just did a survey of the BioConductor repository and only 4 of the 354
> .Rnw vignette files contain the \usepackage{Sweave} specification.
> Adding this is tedious, but not impossible. If the \usepackage{Sweave}
> specification d
Thanks Duncan,
I just did a survey of the BioConductor repository and only 4 of the 354
.Rnw vignette files contain the \usepackage{Sweave} specification.
Adding this is tedious, but not impossible. If the \usepackage{Sweave}
specification does become recommended, could you add a WARNING to the
On 4/9/2008 9:50 PM, Patrick Aboyoun wrote:
> I forgot to mention the BioConductor Windows build machine is running
> Microsoft Windows Server 2003 R2
> Enterprise Edition, SP2
>
> I just checked and this same problem exists if I place R in the standard
> "C:\Program Files\R" location on this mac
I forgot to mention the BioConductor Windows build machine is running
Microsoft Windows Server 2003 R2
Enterprise Edition, SP2
I just checked and this same problem exists if I place R in the standard
"C:\Program Files\R" location on this machine.
For now the backup plan is to move to using short
On 09/04/2008 5:23 PM, Patrick Aboyoun wrote:
> Something funky happened to my e-mail. I was trying to paste information
> related to MiKTeX and R into my message and it appears to have corrupted
> the text somehow. Anyway, the message I was trying to get across is that
> the tex file contains t
Something funky happened to my e-mail. I was trying to paste information
related to MiKTeX and R into my message and it appears to have corrupted
the text somehow. Anyway, the message I was trying to get across is that
the tex file contains the path
\usepackage{E:/paboyoun/BBS-2~1.2-B/R/share/
In the process of updating R to R 2.7 alpha or R 2.7 beta for the
BioConductor 2.2 builds on Windows, I have hit a snag because the BioC
build system has long path names (e.g. D:\biocbld\bbs-2.2-bioc\R) and
these path names are not resolving properly by MiKTeX 2.7 during
vignette construction.
11 matches
Mail list logo
