similar to: Nested tracing with custom callback

I can't seem to reliably obtain parse data via getParseData() for functions from installed packages. The parse data seems to be available only for the *last* file in the package. See [1] for a small example package with just two functions f and g in two files a.R and b.R. See [2] for a documented test run on installed package (Ubuntu 15.10, UTF-8 locale, R 3.2.3). Same behavior with

Hello R experts, I plan to develop a tool for dynamic analysis of R programs. I would like to trace function calls at runtime, capturing argument and return values. Following a suggestion made some time ago on this list, my high-level implementation strategy is to rewrite the AST, augmenting call expressions with pre-call and post-call shims to capture the arguments and return value,

Hi All; This problem has come about from trying to learn some of the review practices recommend by rOpensci. One of them is to use the package goodpractice. After installing goodpractice, it kept failing on my own packages which are under development, and I was concerned something was funny in my own , so I have a fork of the package rerddap, and I tested goodpractice on that. I get the

withr:::set_makevars() can give that error if the makefile named by the 'old_path' argument (default "~/.R/Makevars) contains more than one definition of a variable of the form 'name=value'. You can see what file it is reading and its contents by using the trace() function: trace(withr:::set_makevars, quote({ cat(old_path, "\n"); writeLines(paste0(" ",

As Michael guessed my main use cases was code analysis. A concrete example where this would help is with my test code coverage tool covr. There is currently a bug when tracking coverage for if / else statements when the clauses do not contain brackets (https://github.com/jimhester/covr/issues/39). Because only one source reference is generated in this case (because it is parsed as a single

Probably need a generic tree based on "ParseNode" objects that associate the line information with the symbol (for leaf nodes). As Duncan notes, it should be possible to gather that from the table. But it would be nice if there was an "expr" column in the parse data column in addition to "text". It would contain the parsed object. Otherwise, to use the table, one is

Hi all, I recently proposed a change in R that has led to the addition of new code to the R source code. The code added, as far as I know, has no tests and it might affect many packages in CRAN. I was wondering if adding a test would be helpful or it is already covered by some other test. Which brought me to the question: what is the coverage of R checks (check-devel)? My searches in the

The attached patch to the qemu emulation of the pcnet hardware fixes several problems. It will now only read and write a transmit or receive descriptor once. It will correctly handle transmitting frames with more than two fragments. It will discard oversize frames instead of corrupting memory. I have tested all the changes I have made and even seen an improvement in receive performance from

I have encountered a situation where I would like to use tftp-hpa to retrieve a file that resides within an absolute path containing a ':' character. Ala, "tftp foobar -c get C:2/tftpdir/myfile". Since the tftp client automatically converts the host:file syntax, I get an error "tftp: C: Unknown host". I made a chage to the tftp client code to add a literal mode (-l),

On Wed, 14 Mar 2018, Jeff Newmiller wrote: > Nothing you have said tells me you have LaTeX working (a binary install of > R does not depend on it), but if you actually know it is installed and > available to R then that isn't the problem. Since you have not said what > you actually did or what errors you encountered I can only shrug and > suggest that that the website is a

Hello: Clicking "Knit Word" in RStudio 0.99.893 with R 3.3.0, works fine with a vignette with "output: word_document". However, "R CMD build" throws the following error: $ R CMD build pkgW2vignettes * checking for file ?pkgW2vignettes/DESCRIPTION? ... OK * preparing ?pkgW2vignettes?: * checking DESCRIPTION meta-information ... OK * installing the

I'm running "R CMD check" for 600+ of the packages that depend on survival, and at the end look for ??? grep Status *.Rcheck/00check.log? | grep ERROR to find any that failed.?? But by accident I just looked at the log for the Greg package, which finishes with the lines found below.? Is the final note of WARNING rather than ERROR on purpose, or an error??? If the former, will

Greetings. The group that I work with has just started using the approach outlined in Karl Broman's handy primer: http://kbroman.org/pkg_primer/pages/vignettes.html to create vignettes for a couple of R packages. This works fine as long as we have a current Rmd version of the vignette. But we have some old PDF documents that we'd like to include as vignettes as well. I'd like

Re-submitted for 0.44. b.t.w. I notice that the new 0.44 'R' option is not documented in the tftp man page. ----------------------------------------- I have encountered a situation where I would like to use tftp-hpa to retrieve a file that resides within an absolute path containing a ':' character. Ala, "tftp foobar -c get C:2/tftpdir/myfile". Since the tftp client

Dear Duncan, Thanks for chiming in. Could you explain how you set debug() on post_processor()? I've tried adding debug(post_processor) to rsos_article() or adding debug(post_processor) when after post_processor was defined in the debugger. Neither work for me. All supporting files are available within the package. The code below should be reproducible on your machine.

Thanks, Duncan. The files in question are Emacs Org-mode files, and I think these are more or less isomorphic to Rmd files, but I haven't used Org-mode in a long time, so I think the mapping (Org-mode ==> Rmd) would be painful. -- Mike On Mon, Feb 19, 2018 at 1:20 AM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > On 18/02/2018 9:06 PM, Michael Hannon wrote: >>

Buenas noches, Escribo este mail porque tengo un problema con rmarkdown, estoy creando un informe y me iba bien al generarlo como pdf, de repente me sale el siguiente error y no sé como solucionarlo: pandoc.exe: Error producing PDF from TeX sourceError: pandoc document conversion failed with error 43Además: Warning message:comando ejecutado '"C:/Program

I've found two problems in interpreting adv-r-master/book/build-book.r: 1. All pathes in build-book.r refer to the starting-directory "adv-r-master". However, the script build-book.r is located in the directory "book", which is located in directory "adv-r-master". Therefore, pathes starting at "." are wrong (should start at ".."). 2. Some

Dear all, I'm trying to write a post_processor() for a custom rmarkdown format. The goal of the post_processor() is to modify the latex file before it is compiled. For some reason the post_processor() is not run. The post_processor() does work when I run it manually on the tex file. Any suggestions on what I'm doing wrong? Below is the relevant snippet of the code. The full code is

On 07/09/2017 2:04 PM, Duncan Murdoch wrote: > On 07/09/2017 10:11 AM, Thierry Onkelinx wrote: >> Dear Duncan, >> >> Thanks for chiming in. Could you explain how you set debug() on >> post_processor()? I've tried adding debug(post_processor) to >> rsos_article() or adding debug(post_processor) when after post_processor >> was defined in the debugger.