similar to: 87668 fails on Windows 10 with "pdflatex not found"

Am 29.01.25 um 20:20 schrieb Avraham Adler: > I see there have been a number of tweaks to the document build > recently (87650, 87654, 87658, 97660, 97661, etc.) To Rd2pdf, yes, mostly bug fixes for some rare usages. Some more changes are in the making, also for texi2pdf (but that has not been touched yet). > > I tried building 87668 today on Windows 10 and received the error >

The builder runs tools::texi2pdf() on the vignettes. Does that give the same error for you? Do earlier revisions work? Duncan Murdoch On 2025-01-29 2:20 p.m., Avraham Adler wrote: > I see there have been a number of tweaks to the document build > recently (87650, 87654, 87658, 97660, 97661, etc.) > > I tried building 87668 today on Windows 10 and received the error > below. Is

Dear list, On Fedora 8 I downloaded the beta version of R via svn. make and make check-all worked fine, but make vignettes is failing with: make[1]: Entering directory `/home/gavin/R/2-7-patched/build/src/library' building/updating vignettes for package 'grid' ... processing 'displaylist.Snw' /usr/bin/texi2dvi: pdflatex exited with bad status, quitting. Error in

A kind member of R-core suggested this is due to a misconfiguration on my system, and to post it to the mailing list for troubleshooting. When trying to build R version 4.3.3, in at least two places during the process it gives LaTeX errors of the form: (example 1) you should 'make docs' now ... make[1]: Entering directory '/home/btyner/R-4.3.3/doc' creating

Hello, I'm running R2.10, Eclipse, StatEt and MikTex 2.8 to create Sweave documents, and everything seems to work great, until today... I was trying to add citations from a Bibtex file, but I just got [?] citations. However, if I open the .tex file that StatEt created in MikTex and run the latex+bibtex+pdflatex command, the citations are present. Does anyone know how to either configure

? Fri, 1 Mar 2024 10:46:53 -0500 Benjamin Tyner <btyner at gmail.com> ?????: > my platform info: > > Platform: x86_64-pc-linux-gnu (64-bit) > Running under: Ubuntu 22.04.4 LTS Quick things first: have you installed all the build-dependencies? apt build-dep r-base (maybe with --install-suggests? haven't tried that in a while) should do that. In particular, the build

I am running the beta test version of Ubuntu 9.10, x86_64 on a machine and encountered some peculiarities in LaTeX called through R-devel CMD texi2pdf file.tex The tilde character in the input, which should produce a non-breaking space, is now being rendered as a tilde. Does anyone know where I could begin exploring for explanations and/or workarounds?

Where can I found hepl about latex errors: the R CMD check tells me less, but: * checking PDF version of manual ... WARNING LaTeX errors when creating PDF version. This typically indicates Rd problems. * checking PDF version of manual without hyperrefs or index ... ERROR Re-running with no redirection of stdout/stderr. Hmm ... looks like a package Error in texi2dvi(file = file, pdf = TRUE, clean

Hi. Q. Is there a way to record a plot using grDevices::recordPlot() without opening an interactive (=visible GUI window) graphics device (not even for a flash of a second)? Related: help("recordPlot", package="grDevices") says: "These functions record and replay the displaylist of the current graphics device." Is the intention that recordPlot() should be able to

The documentation for recordPlot says the following: > As of R 3.3.0, it is possible (again) to replay a plot from another R session using, for example, saveRDS and readRDS. However, I haven't been able to save and restore a plot displaylist and have it work within the same R session, using R 3.4.3 or 3.3.3. Here's an example: # Save displaylist for a simple plot

On 21/05/2017 10:30 AM, Peter Carbonetto wrote: > Hi, > > I uncovered a bug in installing R 3.4.0 from source in Linux, following the > standard procedure (configure; make; make install). Is this an appropriate > place to report this bug? If not, can you please direct me to the > appropriate place? Generally R-devel is better; I've responded there. > > The error

Hi, I uncovered a bug in installing R 3.4.0 from source in Linux, following the standard procedure (configure; make; make install). Is this an appropriate place to report this bug? If not, can you please direct me to the appropriate place? The error occurs only when I do "make clean" followed by "make" again; make works the first time. The error is a failure to build

Hi, I uncovered a bug in installing R 3.4.0 from source in Linux, following the standard procedure (configure; make; make install). Is this an appropriate place to report this bug? If not, can you please direct me to the appropriate place? The error occurs only when I do "make clean" followed by "make" again; make works the first time. The error is a failure to build

>>>>> Paul Murrell <paul at stat.auckland.ac.nz> >>>>> on Tue, 3 Apr 2018 09:41:56 +1200 writes: > Hi What you are doing "wrong" is loading a recordedplot > into the same session that it was created in. The > saveRDS()/readRDS() works if you save in one R session and > then read in a different R session. The

On 5/5/07, Prof Brian Ripley <ripley at stats.ox.ac.uk> wrote: [...] > You meam as in > > o dev.interactive() regards devices with the displaylist enabled > as interactive, and packages can register the names of their > devices as interactive via deviceIsInteractive(). > > ? Quick follow up: the displaylist based detection is working well, but

I am having good success in using pdf() to produce pdf graphics files for inclusion in documents processed by pdflatex [I'm using R 1.6.0 on Linux]. I am having one small problem consistently though, which I believe I also had with S-Plus's pdf.graph(): wasted space at the top of the graph which causes pdflatex to put the graph on a later page, when the current page has plenty of space.

Hello, I found my Rnw file generated strange symbols in pdf file. For instance, on page 4 of the following file, http://cran.r-project.org/web/packages/cts/vignettes/kf.pdf you can see Belcher et~al on line 2, and Figure~1 on line 5. The symbol ~ should not appear in the pdf file although the symbol was in the original Rnw file (something like Figure~\ref{...}, section~\ref{...}). On page 1,

Dear Rxperts, Apologize for posting it to a wrong thread..Hence, the re-post... I am trying to use pdflatex from Hmisc, I get the error message. "pdflatex is not available"... The version of Hmisc is the latest one (got the warning that it was compiled under R version 2.15.3) . The version of R on my machine is > version platform i386-w64-mingw32 arch i386 os

Hi, I am trying to produce incremental plots directly using the pdf device. I mean that I want to produce a plot, save it in a pdf file, then add details and save the new plot in a new file, and so on. Before I used to do this with x11, by just adding graphics to a plot and then using dev.copy2eps at the right times for each eps figure. Now I want to do this in batch mode and the x11 device is not

Dear lists: I am somewhat puzzled by the use of texi2dvi/pdflatex in R2.7.0. When building EBImage (bioconductor) with 2.7.0 I get the same error both in Windows and Linux, which reads the following: ** building package indices ... * DONE (EBImage) * creating vignettes ... ERROR /usr/bin/texi2dvi: pdflatex exited with bad status, quitting. Error in texi2dvi(file = bft, pdf = TRUE, clean =