On 19/12/2017 5:20 PM, Georgi Boshnakov wrote:
Sure, but \dontrun's function is to prevent the R tools from running the
enclosed code.
How it is rendered is a completely separate matter. The code in \dontrun is
not required to be executable (or even valid R code), so surely there should be
Sure, but \dontrun's function is to prevent the R tools from running the
enclosed code.
How it is rendered is a completely separate matter. The code in \dontrun is
not required to be executable (or even valid R code), so surely there should be
some sort of visual clue in the rendered page. I
> This actually is not about Rd format. Indeed, you are using 'roxygen'
> syntax.
This is unrelated to roxygen. \dontrun{} is Rd formatting.
Hadley
--
http://hadley.nz
__
R-package-devel@r-project.org mailing list
… and my point was that it is not a matter of syntax, but that the user would
better be alerted.
A user would be more confused and even irritated if they run an example and get
surprises (such as having to wait a long time) or not getting any wiser.
The example you cite falls into the category
On 19/12/2017 10:27 AM, Blume Christine wrote:
Hi Duncan,
Thanks a lot! Good to see that you had a similar idea, I did just
that...in my example it looks like this, however, that does not help,
i.e. that is the code that is associated with the warning…
data(sleepstudy)
wd <- getwd()
name
Actually, the report I received refers to the old 0.7 version…for whatever
reason? The version I had submitted was 0.8 in which I had corrected this.
Well, let’s see…
Another issue seems to be that the text file the example is supposed to read in
is not read (properly) using Debian:
Yes, I used oxygen. My point was that a majority of users is not familiar
Rd/oxygen and if somebody sees something like:
```
Examples
## Not run:
modify_message(12345, add_labels='label_1')
modify_message(12345, remove_labels='label_1')
#add and remove at the same time
modify_message(12345,
2017-12-19 16:27 GMT+01:00 Blume Christine :
> Hi Duncan,
>
> Thanks a lot! Good to see that you had a similar idea, I did just that...in
> my example it looks like this, however, that does not help, i.e. that is the
> code that is associated with the warning…
>
>
Hi Duncan,
Thanks a lot! Good to see that you had a similar idea, I did just that...in my
example it looks like this, however, that does not help, i.e. that is the code
that is associated with the warning…
data(sleepstudy)
wd <- getwd()
name <- "sleepstudy_example"
newdir <-
On 19/12/2017 6:15 AM, Sarah Friedrich wrote:
Dear all,
the CRAN Package Check Results for my package GFD indicate an error on
windows (https://cran.r-project.org/web/checks/check_results_GFD.html),
which I am unable to fix. In my package, I'm using RGtk2 for creating a
GUI. Since this produced
Dear Community,
For Fedora my package now gives a warning message when running the example:
"Warning: working directory was changed to
'/data/gannet/ripley/R/packages/tests-clang/nparACT.Rcheck/sleepstudy_example',
resetting"
I do not really know how to approach/solve this, what has
Dear all,
the CRAN Package Check Results for my package GFD indicate an error on
windows (https://cran.r-project.org/web/checks/check_results_GFD.html),
which I am unable to fix. In my package, I'm using RGtk2 for creating a
GUI. Since this produced errors before, I first check if RGtk2 is
On 19 December 2017 at 13:41, Ralf Stubner wrote:
| On 19.12.2017 09:38, Baptiste Auguie wrote:
| > Thanks for the pointer to `arma::solve_opts::no_band`, it sounds like a
| > good solution (assuming the compiler will then skip all the parts
| > related to banded inversion routines). I've been
13 matches
Mail list logo