search for: parselatex

...sues/1503 ------------------------------ > > Message: 2 > Date: Thu, 20 Jul 2023 23:48:44 +0300 > From: Ivan Krylov <krylov.r00t at gmail.com> > To: Antoine Fabri <antoine.fabri at gmail.com> > Cc: R-devel <r-devel at r-project.org> > Subject: Re: [Rd] tools::parseLatex() crashes on "\\verb{}" > Message-ID: <20230720234844.004b13c2 at Tarkus> > Content-Type: text/plain; charset="us-ascii" > > On Thu, 20 Jul 2023 21:41:44 +0200 > Antoine Fabri <antoine.fabri at gmail.com> wrote: > > > tools::parseLatex("\...

...ng here. As defined in "Parsing Rd files" [*], \code{} blocks are supposed to contain syntactically valid R code. When something that is not valid R is given in a Markdown code block, roxygen2 should not output \code{}, so it outputs \verb{}. Also, unlike in LaTeX as understood by tools::parseLatex(), \verb{} blocks use the {} braces in R documentation, and are understood correctly by tools::parse_Rd(). Perhaps you also need tools::parse_Rd()? -- Best regards, Ivan [*] https://developer.r-project.org/parseRd.pdf

...quot;Parsing Rd > files" [*], \code{} blocks are supposed to contain syntactically valid > R code. When something that is not valid R is given in a Markdown code > block, roxygen2 should not output \code{}, so it outputs \verb{}. > > Also, unlike in LaTeX as understood by tools::parseLatex(), \verb{} > blocks use the {} braces in R documentation, and are understood > correctly by tools::parse_Rd(). Perhaps you also need tools::parse_Rd()? > > -- > Best regards, > Ivan > > [*] https://developer.r-project.org/parseRd.pdf > [[alternative HTML version deleted...

...as nsmall to format(). (Wish of PR#9574) ? legend() supports title.adj. (Wish of PR#13415) ? Added support for subsetting "raster" objects, plus assigning to a subset, conversion to a matrix (of colour strings), and comparisons (== and !=). ? Added a new parseLatex() function (and related functions deparseLatex() and latexToUtf8()) to support conversion of bibliographic entries for display in R. ? Text rendering of \itemize in help uses a Unicode bullet in UTF-8 and most single-byte Windows locales. ? Added support for polygons wit...

...as nsmall to format(). (Wish of PR#9574) ? legend() supports title.adj. (Wish of PR#13415) ? Added support for subsetting "raster" objects, plus assigning to a subset, conversion to a matrix (of colour strings), and comparisons (== and !=). ? Added a new parseLatex() function (and related functions deparseLatex() and latexToUtf8()) to support conversion of bibliographic entries for display in R. ? Text rendering of \itemize in help uses a Unicode bullet in UTF-8 and most single-byte Windows locales. ? Added support for polygons wit...

...he same way points() long has. o Parse errors when installing files now correctly display the name of the file containing the bad code. o In Windows, tcltk windows were not always properly constructed. (PR#15150) o The internal functions implementing parse(), tools::parseLatex() and tools::parse_Rd() were not reentrant, leading to errors in rare circumstances such as a garbage collection triggering a recursive call. o Field assignments in reference class objects via $<- were not being checked because the magic incantation to turn methods o...

...he same way points() long has. o Parse errors when installing files now correctly display the name of the file containing the bad code. o In Windows, tcltk windows were not always properly constructed. (PR#15150) o The internal functions implementing parse(), tools::parseLatex() and tools::parse_Rd() were not reentrant, leading to errors in rare circumstances such as a garbage collection triggering a recursive call. o Field assignments in reference class objects via $<- were not being checked because the magic incantation to turn methods o...