Yes, most open-source software on Mac OS X is old. One issue is
GPL-3: texinfo was an early adopter, and AFAIR texinfo 4.8 was the
last GPL-2 release.
My point was (and remains) that if you have your paths set up
correctly, tools::texi2dvi will use the texi2dvi script and not
pdflatex direct
On 05-07-2011, at 17:39, Prof Brian Ripley wrote:
> On Tue, 5 Jul 2011, Federico Calboli wrote:
>
>> On 5 Jul 2011, at 16:26, Kasper Daniel Hansen wrote:
which texi2dvi
/usr/bin/texi2dvi
and
$:/usr/local/texlive/2010/bin/x86_64-darwin$ ls texi*
texindy
On 5 Jul 2011, at 19:58, Timothy Bates wrote:
> I’d like to send an applescript command to R.app (from Textmate) to clear the
> console (as is achieved by “Edit:Clear Console”)
>
> Is there an R function that achieves that, or calls R.app’s menu items?
Hi Tim,
simply call this AppleScript whic
Dear R-guys,
I’d like to send an applescript command to R.app (from Textmate) to clear the
console (as is achieved by “Edit:Clear Console”)
Is there an R function that achieves that, or calls R.app’s menu items?
Best, tim
--
The University of Edinburgh is a charitable body, registered in
Scotl
On Tue, 5 Jul 2011, Federico Calboli wrote:
On 5 Jul 2011, at 16:26, Kasper Daniel Hansen wrote:
which texi2dvi
/usr/bin/texi2dvi
and
$:/usr/local/texlive/2010/bin/x86_64-darwin$ ls texi*
texindy
but no texi2dvi. I did ask other mactex users and they also do not have texi2dvi
Well, I have
On 5 Jul 2011, at 16:26, Kasper Daniel Hansen wrote:
>>
>> which texi2dvi
>> /usr/bin/texi2dvi
>>
>> and
>>
>> $:/usr/local/texlive/2010/bin/x86_64-darwin$ ls texi*
>> texindy
>>
>> but no texi2dvi. I did ask other mactex users and they also do not have
>> texi2dvi
>
> Well, I have texi2dvi a
On Tue, Jul 5, 2011 at 11:23 AM, Federico Calboli
wrote:
> On 5 Jul 2011, at 16:01, Prof Brian Ripley wrote:
>
>> And note too that this is looking first for a script texi2dvi. If you have
>> that, *it* will look for pdflatex, possibly already knowing where to look.
>>
>> Also note that both the
On 5 Jul 2011, at 16:01, Prof Brian Ripley wrote:
> And note too that this is looking first for a script texi2dvi. If you have
> that, *it* will look for pdflatex, possibly already knowing where to look.
>
> Also note that both the usual texi2dvi and tools::texi2dvi will consult
> environment
And note too that this is looking first for a script texi2dvi. If you
have that, *it* will look for pdflatex, possibly already knowing where
to look.
Also note that both the usual texi2dvi and tools::texi2dvi will
consult environment variables such as PDFLATEX.
If you have a standard Mac Te
On 5 Jul 2011, at 15:19, Simon Urbanek wrote:
>
> But that is largely irrelevant to R. R has its own mechanisms that are well
> documented in the R documentation, so you can use environment.plist or
> .profile if you are so inclined, but I would not recommend it, mainly because
> it will still
On Jul 5, 2011, at 9:48 AM, David Winsemius wrote:
>
> On Jul 5, 2011, at 9:10 AM, Federico Calboli wrote:
>
>> Simon,
>>
>>> both are entirely irrelevant - run
>>> system("pdflatex --version")
>>> in R - that is the only thing that counts. If it shows an error, then you
>>> don't have pdflat
On Jul 5, 2011, at 9:10 AM, Federico Calboli wrote:
> Simon,
>
>> both are entirely irrelevant - run
>> system("pdflatex --version")
>> in R - that is the only thing that counts. If it shows an error, then you
>> don't have pdflatex on your PATH which would be the problem. As a side note,
>> y
Hi,
To alter the PATH variables that your GUI apps see, you need to play
with your ~/.MacOSX/environment.plist file -- or apparently even
messing with /etc/launchd.conf (if you launch with spotllight, I
guess).
See here:
http://stackoverflow.com/questions/135688/setting-environment-variables-in-o
On 5 July 2011 15:00, Federico Calboli wrote:
> On 5 Jul 2011, at 14:48, David Winsemius wrote:
>
>> On Jul 5, 2011, at 9:10 AM, Federico Calboli wrote:
>>
>>> Simon,
>>>
both are entirely irrelevant - run
system("pdflatex --version")
in R - that is the only thing that counts. If it
On 5 Jul 2011, at 14:48, David Winsemius wrote:
> On Jul 5, 2011, at 9:10 AM, Federico Calboli wrote:
>
>> Simon,
>>
>>> both are entirely irrelevant - run
>>> system("pdflatex --version")
>>> in R - that is the only thing that counts. If it shows an error, then you
>>> don't have pdflatex on y
On Jul 5, 2011, at 9:10 AM, Federico Calboli wrote:
Simon,
both are entirely irrelevant - run
system("pdflatex --version")
in R - that is the only thing that counts. If it shows an error,
then you don't have pdflatex on your PATH which would be the
problem. As a side note, you are showing
Simon,
> both are entirely irrelevant - run
> system("pdflatex --version")
> in R - that is the only thing that counts. If it shows an error, then you
> don't have pdflatex on your PATH which would be the problem. As a side note,
> you are showing two separate TeX packages which may not help you
Federico,
both are entirely irrelevant - run
system("pdflatex --version")
in R - that is the only thing that counts. If it shows an error, then you don't
have pdflatex on your PATH which would be the problem. As a side note, you are
showing two separate TeX packages which may not help you to fin
On 5 Jul 2011, at 10:44, Federico Calboli wrote:
>
> My comment is, pdflatex *is* availiable:
>
> $ :/usr/local/texlive/2010/bin/universal-darwin$ ls -l pdflatex
> lrwxr-xr-x 1 root wheel 6 21 Oct 2010 pdflatex -> pdftex
>
> and
>
> $ :/usr/local/texlive/2010/bin/x86_64-darwin$ ls -l pdfla
Hi All,
I am building a package on my MBP (latest R, latest OSX, TexLive 2010), and I
am incurring in some annoying problems with R CMD check:
* checking PDF version of manual ... WARNING
LaTeX errors when creating PDF version.
This typically indicates Rd problems.
* checking PDF version of manu
20 matches
Mail list logo