In help("pskill", package = "tools") is says:
Only SIGINT and SIGTERM will be defined on Windows, and pskill will
always use the Windows system call TerminateProcess.
As far as I understand it, TerminateProcess [1] terminates the process
"quite abruptly". Specifically, it is not possible for th
fixing
this in R 4.5.0, I'll make this a top priority. Please let me know.
/Henrik
On Thu, Mar 20, 2025 at 3:31 AM Martin Maechler
wrote:
>
> >>>>> Henrik Bengtsson
> >>>>> on Wed, 19 Mar 2025 10:58:46 -0700 writes:
>
> > Hello.
>
On Fri, Mar 21, 2025 at 8:55 AM Martin Maechler
wrote:
>
> >>>>> Martin Maechler
> >>>>> on Fri, 21 Mar 2025 14:49:16 +0100 writes:
>
> >>>>> Henrik Bengtsson
> >>>>> on Thu, 20 Mar 2025 11:55:05 -
you considered making it a
warning of class 'deprecatedWarning'? Not a big deal, but wanted to
mention it, just in case.
/Henrik
On Fri, Mar 21, 2025 at 10:07 AM Henrik Bengtsson
wrote:
>
> On Fri, Mar 21, 2025 at 8:55 AM Martin Maechler
> wrote:
> >
> > >>>&
What's going on here?
$ R --vanilla --quiet
> plot.new(); suppressWarnings({ points(0, 0, foo = TRUE) })
> NULL
NULL
Warning messages:
1: "foo" is not a graphical parameter
2: "foo" is not a graphical parameter
Note how the warnings are revived in that second "NULL" call. I can
reproduce this in
Hello.
I just (re-)discovered that structure(sum, init = 100) is "sticky",
i.e. it stays with base::sum(). Here's an minimal example:
$ R --vanilla --quiet
> void <- structure(sum, some_attr = TRUE)
> str(sum)
function (..., na.rm = FALSE)
- attr(*, "some_attr")= logi TRUE
>From my very basic t
Thanks for looking into this and the patch. FWIW, there's an open
PR18105 - "R CMD build: Add dependency on R >= 4.1.0 if code uses pipe
symbol |>" for this
(https://bugs.r-project.org/show_bug.cgi?id=18105).
/Henrik
On Thu, Jan 16, 2025 at 3:42 AM Ivan Krylov via R-devel
wrote:
>
> Hello R-deve
Can't speak for Jeroen, but it sounds like it's worth adding support
for tar.zstd package files, just like how tar.gz, tar.xz, and
tar.bzip2 are currently supported. I'd also argue for support zstd
compression throughout R, including adding zstdfile(), support for
saveRDS(..., compress = "zstd"), a
On Wed, Apr 24, 2024 at 1:32 PM luke-tierney--- via R-devel
wrote:
>
> On Wed, 24 Apr 2024, Hadley Wickham wrote:
>
> >>
> >>
> >>
> > That is not true at all - the presence of header does not constitute
> declaration of something as the R API. There are cases where internal
> functi
Hello,
thanks for bringing this topic up, and it would be excellent if we
could come of with a generic solution for this in base R. It is one
of the top frequently asked questions and requested features in
parallel processing, but also in sequential processing. We have also
seen lots of variants
On Mon, Mar 4, 2024 at 8:45 AM luke-tierney--- via R-devel
wrote:
>
> Comparison operators == and != can be used on language objects
> (i.e. call objects and symbols). The == operator in particular often
> seems to be used as a shorthand for calling identical(). The current
> implementation involv
Technically, there is a round() for 'Date' objects, but it doesn't
seem very useful, because it basically just fall back to the default
round() method, which only takes the 'digits' argument.
Here's an example:
> date <- Sys.Date()
> class(date)
[1] "Date"
We see that there are only two round()
Here's a dummy example that I think illustrates the problem:
toto <- function() {
if (runif(1) < 0.5)
function(a) a
else
function(a,b) a+b
}
> fcn <- toto()
> fcn(1,2)
[1] 3
> fcn <- toto()
> fcn(1,2)
[1] 3
> fcn <- toto()
> fcn(1,2)
Error in fcn(1, 2) : unused argument (2)
How can y
>
>
>
>
>
> ---- Original Message
> On Jan 6, 2024, 12:38, Henrik Bengtsson < henrik.bengts...@gmail.com> wrote:
>
>
> ISSUE: On MS Windows, running cmd.exe, calling Rscript --vanilla -e "port <-
> tools::startDynamicHelp(); port; port <-
ISSUE:
On MS Windows, running cmd.exe, calling
Rscript --vanilla -e "port <- tools::startDynamicHelp(); port; port <-
tools::startDynamicHelp(FALSE); port"
will sometimes stall R at the end, preventing it from existing. This
also happens when running R in interactive mode. It seems to stem
fro
Careful; tryCatch() on non-error conditions will break out of what's
evaluated, e.g.
res <- tryCatch({
cat("1\n")
message("2")
cat("3\n")
42
}, message = identity)
will output '1' but not '3', because it returns as soon as the first
message() is called.
To "record" messages (same for war
s change too :)
The discussion on whether certain R expressions (e.g. dim(x) <-
dim(x)) should be no-op is interesting, but it's much bigger, and I
can see how it becomes a quite complicated discussion.
Thanks,
Henrik
On Mon, Oct 30, 2023 at 3:53 AM Martin Maechler
wrote:
>
>
&g
Hello,
the fix of PR18612 (https://bugs.r-project.org/show_bug.cgi?id=18612)
in r85380
(https://github.com/wch/r-source/commit/2653cc6203fce4c48874111c75bbccac3ac4e803)
caused a change in `dim<-()`. Specifically, in the past, any
`dim<-()` assignment would _always_ remove "dimnames" and "names"
This is actually not a bug. If we really want to identify a bug, then
it's actually a bug in your code. We'll get to that at the very end.
Either way, it's an interesting report that reveals a lot of things.
First, here's a slightly simpler version of your example:
$ Rscript --vanilla -e 'library
On Thu, May 4, 2023 at 3:02 PM Serguei Sokol via R-devel
wrote:
>
> Le 03/05/2023 à 01:25, Henrik Bengtsson a écrit :
> > Along the lines of calling R_CheckUserInterrupt() only onces in a while:
> >
> >> OTOH, in the past we have had to *disable* R_CheckUserInterrupt(
Along the lines of calling R_CheckUserInterrupt() only onces in a while:
> OTOH, in the past we have had to *disable* R_CheckUserInterrupt()
> in parts of R's code because it was too expensive,
> {see current src/main/{seq.c,unique.c} for a series of commented-out
> R_CheckUserInterrupt() for su
A quick drive-by-comment: What if 'R CMD build' would have an option
to flatten R/ subfolders when building the tarball, e.g.
R/unix/a.R
R/windows/a.R
R/a.R
becomes:
R/00__unix__a.R
R/00__windows__a.R
R/a.R
? Maybe that would be sufficient for most use cases. The only thing
I can imagine is t
Not sure who is the webadmin for
https://cran.r-project.org/sources.html, so posting it here:
I just noticed it's not straightforward to find the Subversion URL for
the R source code. A natural search would be to go to
https://cran.r-project.org/, then click 'Source code' to get to
https://cran.r
I'd like to be able to prevent the <<- assignment operator ("super
assignment") from assigning to the global environment unless the
variable already exists and is not locked. If it does not exist or is
locked, I'd like an error to be produced. This would allow me to
evaluate expressions with this
> Your best bet really to govern your .libPaths from your Rprofile.site and
Renviron.site ...
To do this for any version of R, one can add:
R_LIBS_USER=~/.local/share/R/%p-library/%v
to ~/.Renviron or the Renviron.site file. This automatically expands
to the platform and R x.y version early on w
On Wed, Feb 8, 2023 at 12:22 PM Iñaki Ucar wrote:
>
> On Wed, 8 Feb 2023 at 19:59, Henrik Bengtsson
> wrote:
> >
> > I just want to add a few reasons that I know of for why users are
> > still on Red Hat/CentOS 7 and learned from being deeply involved with
> &g
Thanks for this work. My suggestion would be to provide those
pre-built Windows binaries to maximize the chances to get the feedback
you need. The amount of people ready to, or have the setup to, build R
from source, especially so on MS Windows, is much smaller than those
who are willing to give it
I just want to add a few reasons that I know of for why users are
still on Red Hat/CentOS 7 and learned from being deeply involved with
big academic and research high-performance compute (HPC) environments.
These systems are not like your regular sailing boat, but more like a
giant container ship;
;t want to make a decision.
>
> I don't have a strong opinion on this, but Sys.getenv("FOO") and
> Sys.getenv()[["FOO"]] should not yield two different results. I would argue
> that if we want to make specific checks, we should make them conditional -
> eve
/Hello.
SUMMARY:
$ BOOM=$'\xFF' LC_ALL=en_US.UTF-8 Rscript --vanilla -e "Sys.getenv()"
Error in substring(x, m + 1L) : invalid multibyte string at ''
$ BOOM=$'\xFF' LC_ALL=en_US.UTF-8 Rscript --vanilla -e "Sys.getenv('BOOM')"
[1] "\xff"
BACKGROUND:
I launch R through an Son of Grid Engine (SGE)
I've moved this to https://bugs.r-project.org/show_bug.cgi?id=18443.
/Henrik
On Wed, Nov 30, 2022 at 2:03 PM Henrik Bengtsson
wrote:
>
> BACKGROUND:
>
> In recent versions of R-devel, sessionInfo() has a 'tzone' element, e.g.
>
> > sessionInfo()$tzone
>
BACKGROUND:
In recent versions of R-devel, sessionInfo() has a 'tzone' element, e.g.
> sessionInfo()$tzone
[1] "America/Los_Angeles"
ISSUE:
Some time zones, like the one above, has an underscore. This
underscore is *not* escaped by utils:::toLatex.sessionInfo, e.g.
$ TZ="America/Los_Angeles"
ailure, not 0, so the test on ifd (and I suppose
> > also the one on ifp) is wrong. And of course, once you close file
> > descriptor 0, mkstemp() chooses the 1st available fd, i.e. 0, for its
> > return value.
> >
> > -pd
> >
> >> On 9 Oc
Rscript fails to launch if the standard input (stdin) is closed, e.g.
$ Rscript --vanilla -e 42 0<&-
Fatal error: creating temporary file for '-e' failed
This appear to only happen with `-e EXPR`, e.g. it works when doing:
$ echo "42" > script.R
$ Rscript --vanilla script.R 0<&-
[1] 42
and:
$
Excluding the global environment, and all its parent environments from
the search path that a package sees would be great news, because it
would makes things more robust and probably detect a few more bugs out
there. In addition to the use case that Duncan mentions, it would
also remove the ambigu
> ... The extra apostrophe does not seem to have created an issue during all
> those tests, or since, under either Debian or Ubuntu.
I think that is because the system library '/usr/lib/R/library' is
always appended at the end of the library path, so that non-existing
to folder (the one with the
On MS Windows 10, the following works:
> Rscript --vanilla -e "\"abc\""
[1] "abc"
and also:
> Rterm --vanilla --no-echo -e "\"abc.txt\""
[1] "abc.txt"
whereas attempting the same with 'R' fails;
> R --vanilla --no-echo -e "\"abc.txt\""
Error: object 'abc' not found
Execution halted
I get this
Simon's suggestion with withCallingHandlers() is the correct way.
Also, note that if you use tryCatch() to catch warnings, you're
*interrupting* the evaluation of the expression of interest, e.g.
> res <- tryCatch({ message("hey"); warning("boom"); message("there"); 42 },
> warning = function(w)
Hi,
in R 4.1.2 we have:
> x <- structure(as.list(1:2), dim = c(1,2))
> x
[,1] [,2]
[1,] 12
> as.vector(x, mode = "list")
[,1] [,2]
[1,] 12
whereas in recent versions of R-devel (4.2.0) we have:
> x <- structure(as.list(1:2), dim = c(1,2))
> x
[,1] [,2]
[1,] 12
> as.ve
Hi,
in R-devel (4.2.0), we now get:
> mapply(paste, "A", character(), USE.NAMES = TRUE)
named list()
Now, in ?mapply we have:
USE.NAMES: logical; use the names of the first ... argument, or if
that is an unnamed character vector, use that vector as the names.
This basically says we should get:
On Tue, Nov 23, 2021 at 12:06 PM Gábor Csárdi wrote:
>
> On Tue, Nov 23, 2021 at 8:49 PM Henrik Bengtsson
> wrote:
> >
> > > Is there any reliable way to let packages to know if they are on CRAN, so
> > > they can set omp cores to 2 by default?
> >
>
> Is there any reliable way to let packages to know if they are on CRAN, so
> they can set omp cores to 2 by default?
Instead of testing for "on CRAN" or not, you can test for 'R CMD
check' running or not. 'R CMD check' sets environment variable
_R_CHECK_LIMIT_CORES_=TRUE. You can use that to lim
Hi,
the following question sprung out of a package settings option warn=-1
to silence warnings, but those warnings were still caught by
withCallingHandlers(..., warning), which the package author did not
anticipate. The package has been updated to use suppressWarnings()
instead, but as I see a lot
I'm trying to reuse some of the translations available in base R by using:
gettext(msgid, domain="R")
This works great for most 'msgid's, e.g.
$ LANGUAGE=de Rscript -e 'gettext("cannot get working directory", domain="R")'
[1] "kann das Arbeitsverzeichnis nicht ermitteln"
However, it does not
olution at the time (May 2020). See "Dependencies NOTE lost with
> --as-cran" (https://stat.ethz.ch/pipermail/r-package-devel/2020q2/005467.html)
>
> On Wed, Oct 20, 2021 at 11:55 PM Henrik Bengtsson
> wrote:
>>
>> ISSUE:
>>
>> Using 'R CMD chec
environ
$ echo "R_LIBS_USER=[${R_LIBS_USER}]"
R_LIBS_USER=[C:\Users\foobar\AppData\Roaming\R-library]
/Henrik
On Sun, Oct 31, 2021 at 2:59 AM Tomas Kalibera wrote:
>
>
> On 10/31/21 2:55 AM, Henrik Bengtsson wrote:
> >> ... If one still needed backslashes,
> >&g
> ... If one still needed backslashes,
> they could then be entered in single quotes, e.g. VAR='c:\users'.
I don't think it matters whether you use single or double quotes -
both will work. Here's a proof of concept on Linux with R 4.1.1:
$ cat ./.Renviron
A=C:\users
B='C:\users'
C="C:\users"
$
Two comments/suggestions:
1. What about recommending to always quote the value in Renviron
files, e.g. ABC="Hello world" and DEF="${APPDATA}/R-library"? This
should a practice that works on all platforms.
2. What about having readRenviron() escapes strings it imports via
environment variables?
ISSUE:
Using 'R CMD check' with --as-cran,
set_R_CHECK_PACKAGES_USED_IGNORE_UNUSED_IMPORTS_=TRUE, whereas the
default is FALSE, which you get if you don't add --as-cran.
I would expect --as-cran to check more things and more be conservative
than without. So, is this behavior a mistake? Could it
is a property we should
all strive for for other types of objects?
/Henrik
On Thu, Sep 23, 2021 at 12:46 AM Martin Maechler
wrote:
>
> >>>>> Henrik Bengtsson
> >>>>> on Wed, 22 Sep 2021 20:48:05 -0700 writes:
>
> > The update in rev 809
The update in rev 80946
(https://github.com/wch/r-source/commit/d970867722e14811e8ba6b0ba8e0f478ff482f5e)
caused as.character() on hexmode objects to no longer pads with zeros.
Before:
> x <- structure(as.integer(c(0,8,16,24,32)), class="hexmode")
> x
[1] "00" "08" "10" "18" "20"
> as.character(x
new .Random.seed value:
> > runif(1)
> [1] 0.3842704
>
> > sum(.Random.seed)
> [1] -13435151647
>
> # So let's make things really random, by using the new seed as a seed:
> > set.seed(.Random.seed)
> > sum(.Random.seed)
> [1] 24428993419
>
> # B
warning or error with set.seed().
>
> Validating inputs and emitting errors early is a good practice.
>
> Just my 2 cents.
>
> Sincerely.
> Andre GILLIBERT
>
> -Message d'origine-
> De : R-devel [mailto:r-devel-boun...@r-project.org] De la part de Avraham
&g
Hi,
according to help("set.seed"), argument 'seed' to set.seed() should be:
a single value, interpreted as an integer, or NULL (see ‘Details’).
>From code inspection (src/main/RNG.c) and testing, it turns out that
if you pass a 'seed' with length greater than one, it silently uses
seed[1], e.g
Thank you Simon, this is helpful. I take this is specific to quit(),
so it's a poor choice for emulating crashed parallel workers, and
Sys.kill() is much better for that.
I was focusing on that odd extra execution/output, but as you say,
there are lots of other things that is done by quit() here,
The following smells like a bug in R to me, because it puts the main R
session into an unstable state. Consider the following R script:
a <- 42
message("a=", a)
cl <- parallel::makeCluster(1L, type="FORK")
try(parallel::clusterEvalQ(cl, quit(save="no")))
message("parallel:::isChild()=", parallel:
ISSUE:
The TMPDIR validation done in src/gnuwin32/system.c:
/* in case getpid() is not unique -- has been seen under Windows */
snprintf(ifile, 1024, "%s/Rscript%x%x", tm, getpid(),
(unsigned int) GetTickCount());
ifp = fopen(ifile, "w+b");
if(!ifp) R_Suicide(_("creation
On Wed, May 5, 2021 at 2:13 AM Martin Maechler
wrote:
>
> > Gabriel Becker
> > on Tue, 4 May 2021 14:40:22 -0700 writes:
>
> > Hmm, that's fair enough Ben, I stand corrected. I will say that this
> seems
> > to be a pretty "soft" recommendation, as these things go, given that
uot;)
which also produces errors when 'recommended' packages are missing,
e.g. "Failed with error: 'there is no package called 'nlme'".
(*) BTW, '../bin/R CMD make test-BasePackages' gives "make: *** No
rule to make target 'test-BasePack
FWIW,
$ ./configure --help
...
--with-recommended-packages
use/install recommended R packages [yes]
/Henrik
On Tue, May 4, 2021 at 11:17 AM Dirk Eddelbuettel wrote:
>
>
> On 4 May 2021 at 11:07, Henrik Bengtsson wrote:
> | Thanks, but I don't unders
path on purpose
and I'm looking for a way to validate such an installation.
If your comment is on the 'stats' examples' hard dependency on 'MASS'
despite it's being a suggested packages, I still don't follow.
/Henrik
On Tue, May 4, 2021 at 10:16 AM Dir
I'm on Linux (Ubuntu 18.04). How do I check an R build when using
--without-recommended-packages? 'make check' assumes 'recommended'
packages are installed, so that fails without them available.
DETAILS:
When I build R from source without 'recommended' packages:
curl -O https://cran.r-project.or
Ben, it's most like what Peter says. I can confirm it works; I just
installed https://cran.r-project.org/src/base-prerelease/R-latest.tar.gz
on an up-to-date CentOS 7.9.2009 system using the vanilla gcc (GCC)
4.8.5 that comes with that version and R compiles just fine and it
passes 'make check' to
In ?base::.libPaths, there's a paragraph saying:
The library search path is initialized at startup from the environment
variable R_LIBS (which should be a colon-separated list of directories
at which R library trees are rooted) followed by those in environment
variable R_LIBS_USER. Only directorie
Without having dug into the details, it could be that one could update
the parser by making a 'return' a keyword and require it to be
followed by a parenthesis that optionally contains an expression
followed by end of statement (newline or semicolon). Such a
"promotion" of the 'return' statement s
FWIW, 'R CMD check --as-cran' in R-devel checks for "bogus return"
statements but I think that's only for the case when one forgets the
parentheses, e.g. 'return' instead of 'return()'.
I don't think it catches this case but I'm also not sure. Though, I can
imagine it might be possible to enhance
rewalls and it's also extremely tedious. Reverse SSH
tunneling is super simply; all you need to to is something like:
rshopts <- c(sprintf("-R %d:%s:%d", rscript_port, master, port), rshopts)
/Henrik
On Fri, Nov 6, 2020 at 4:37 PM Duncan Murdoch wrote:
>
> On 06/11/2020 4
I've "moved" this to
https://bugs.r-project.org/bugzilla/show_bug.cgi?id=17919 to make sure
it's tracked. /Henrik
On Thu, Sep 3, 2020 at 7:25 AM Dirk Eddelbuettel wrote:
>
>
> On 2 September 2020 at 23:38, Henrik Bengtsson wrote:
> | WORKAROUND:
> | Setting R
ISSUE:
It looks like Rgui.exe never processes ~/.Renviron - only ./.Renviron.
REPRODUCIBLE EXAMPLE:
On Windows, create the following ~/.Renviron and ~/.Rprofile files:
C:\Users\alice> Rscript -e "cat('FOO=123\n', file='~/.Renviron')"
C:\Users\alice> Rscript -e "cat('print(Sys.getenv(\'FOO\'))',
f
Hi, it looks like:
> stats:::`[.formula`
function (x, i)
{
ans <- NextMethod("[")
if (length(ans) == 0L || as.character(ans[[1L]])[1L] == "~") {
class(ans) <- "formula"
environment(ans) <- environment(x)
}
ans
}
doesn't like to extract NULL components on either t
gt;
> Hi Henrik,
>
> A bit late, but you can take a look at smbache's {import} package [1]
> in case you didn't know it. I believe it does what you are describing.
>
> [1] https://github.com/smbache/import
>
> Iñaki
>
> On Tue, 23 Jun 2020 at 22:21, Henrik Bengtsso
Hi,
I'm developing a package whose API is only meant to be used in other
packages via imports or pkg::foo(). There should be no need to attach
this package so that its API appears on the search() path. As a
maintainer, I want to avoid having it appear in search() conflicts by
mistake.
This means
Was this resolved upstream or is this something that R should/could
fix? If the latter, could this also go into the "emergency release" R
4.0.2 that is scheduled for 2020-06-22?
My $.02
/Henrik
On Sun, May 31, 2020 at 8:13 AM Gábor Csárdi wrote:
>
> Btw. it would be also possible to create a m
Interesting problem. I'm very rusty on S4 but would one solution be
to, already now, add 'simplify = TRUE' to the S4 method and document
it;
setMethod("apply", signature(X = "Speclib"),
function(X,
FUN,
bySI = NULL,
...,
On Wed, May 20, 2020 at 11:10 AM brodie gaslam via R-devel
wrote:
>
> > On Wednesday, May 20, 2020, 7:00:09 AM EDT, peter dalgaard
> wrote:
> >
> > Expected, see FAQ 7.31.
> >
> > You just can't trust == on FP operations. Notice also
>
> Additionally, since you're implementing a "mean" function
What's the gist of the problem of making/having this part of the public
API? Is it security, is it stability, is it that the current API is under
construction, is it a worry about maintenance load for R Core, ...? Do we
know why?
It sounds like it's a feature that is useful. I think we missed out
ik,
> >>
> >> That clears things up significantly. I did see the warning but failed to
> >> include it my initial email. It sounds like an RStudio issue, and it seems
> >> like that it’s quite intrinsic to how forks interact with RStudio. Given
&g
Hi, a few comments below.
First, from my experience and troubleshooting similar reports from
others, a returned NULL from parallel::mclapply() is often because the
corresponding child process crashed/died. However, when this happens
you should see a warning, e.g.
> y <- parallel::mclapply(1:2, FU
I'm sure this exists elsewhere, but, as a trade-off, could you achieve
what you want with a separate helper function F(expr) that constructs
the function you want to pass to [lsv]apply()? Something that would
allow you to write:
sapply(split(mtcars, mtcars$cyl), F(summary(lm(mpg ~ wt,.))$r.square
I'd second Jim's feature request - it would be useful to be able to
disable this in CI and elsewhere.The concept of using an "unusual"
version component such as a very large number does a nice job of
indicating "unusual" and serves as a blocker for submitting
work-in-progress to CRAN by mistake
While at it, would it be worth mentioning in the NEWS for R 4.0.0 that
options 'stringsAsFactors' is being deprecated, e.g.
$ options(stringsAsFactors = TRUE)
Warning message:
In options(stringsAsFactors = TRUE) :
'options(stringsAsFactors = TRUE)' is deprecated and will be disabled
? Currentl
sion.
https://bugs.r-project.org/bugzilla/show_bug.cgi?id=15128#c1
/Henrik
On Tue, Mar 20, 2018 at 2:11 PM Henrik Bengtsson
wrote:
>
> Contrary to, say, Sys.setenv(), Sys.setlocale() returns it's value
> visibly. This means that if you for instance add:
>
> Sys.setlocal
cOS - it already
worked as wanted on Windows (see, there's some advantages to be on
that OS).
/Henrik
On Wed, Mar 18, 2020 at 9:38 PM Henrik Bengtsson
wrote:
>
> On Wed, Mar 18, 2020 at 8:04 PM Dirk Eddelbuettel wrote:
> >
> >
> > On 18 March 2020 at 19:19, Henri
On Wed, Mar 18, 2020 at 8:04 PM Dirk Eddelbuettel wrote:
>
>
> On 18 March 2020 at 19:19, Henrik Bengtsson wrote:
> | AFAIU, 'R CMD check --as-cran' tries to hide any site and user package
> | libraries by setting R_LIBS_SITE and R_LIBS_USER. However, contrary
>
AFAIU, 'R CMD check --as-cran' tries to hide any site and user package
libraries by setting R_LIBS_SITE and R_LIBS_USER. However, contrary
to R_LIBS_SITE, it fails for R_LIBS_USER and the user's personal
library is still available for test scripts. Should I revise my
assumptions, or is that inten
Here's a simpler example that should reproduce that error for you:
ans <- utils::select.list(c("hello", "world", "again"), graphics=TRUE)
Does it?
FYI, I installed R 3.6.3 from source on CentOS 7 a few hours ago, and
for me the above works just fine.
For your immediate needs of selecting a CR
;>>> Martin Maechler
> >>>>> on Sat, 29 Jun 2019 10:33:10 +0200 writes:
>
> >>>>> peter dalgaard
> >>>>> on Fri, 28 Jun 2019 16:20:03 +0200 writes:
>
> >>> > On 28 Jun 2019,
On Tue, Jan 14, 2020 at 1:32 PM Marc Schwartz via R-devel
wrote:
>
> > On Jan 14, 2020, at 3:29 PM, Abby Spurdle wrote:
> >
> >> I do want to entice people to have a long look beyond closed
> >> source OS into the world of Free Software where not only R is
> >> FOSS (Free and Open Source Software
umber of R
users we have out there. We have more important things to spend our
time on. I can easily count days wasted due to troubleshooting and
helping others remotely on problems related to instability of forked
processing. Being able to disable it, would have shortcut this quite a
bit.
/Henrik
o sequential processing as well. (I'm aware that not all
use cases of async processing is about parallelization, so it might
not apply everywhere).
Cheers,
Henrik
>
> Cheers,
> Simon
>
>
>
> > On Jan 10, 2020, at 10:58 AM, Henrik Bengtsson
> > wrote:
> >
that in principle the functionality requested here can be easily
> implemented in a package so R doesn’t need to be modified.
>
> Cheers,
> Simon
>
> Sent from my iPhone
>
> >> On Jan 10, 2020, at 04:34, Tomas Kalibera wrote:
> >>
> >> On 1/10/20 7:3
I'd like to pick up this thread started on 2019-04-11
(https://hypatia.math.ethz.ch/pipermail/r-devel/2019-April/077632.html).
Modulo all the other suggestions in this thread, would my proposal of
being able to disable forked processing via an option or an
environment variable make sense? I've pro
On Tue, Jan 7, 2020 at 6:14 AM brodie gaslam via R-devel
wrote:
>
> For whatever my 2c are worth I think this would be nice. I'm still
> uncomfortable at having to call `options` in my package `diffobj` to set
> output width.
Adding a few more cents: It might be worth considering "who" should
This is very exciting news. Luke, thank you for all your work on this
- I know it's been a long journey.
All the best,
Henrik
On Tue, Dec 3, 2019 at 8:04 AM Tierney, Luke wrote:
>
> R-devel has been switched to use reference counting by default with
> r77508. Building with -DSWITCH_TO_NAMED go
Another thing to consider if one wants to anonymize the build is the
UID/GID of the files in the tarball. So there might be a need for a
R_BUILD_UID and R_BUILD_GID, e.g. by setting those to 32767
("nobody").
/Henrik
On Fri, Jan 25, 2019 at 9:25 AM Will L wrote:
>
> Thanks, Kurt.
>
> I think I
On Mon, Nov 18, 2019 at 6:55 AM Tomas Kalibera wrote:
>
> On 11/18/19 3:44 PM, Henrik Bengtsson wrote:
> > .On Mon, Nov 18, 2019 at 12:35 AM Martin Maechler
> > wrote:
> >>>>>>> Henrik Bengtsson
> >>>>>>> on Sun, 17 Nov 20
.On Mon, Nov 18, 2019 at 12:35 AM Martin Maechler
wrote:
>
> >>>>> Henrik Bengtsson
> >>>>> on Sun, 17 Nov 2019 20:42:32 -0800 writes:
>
> > Hi,
>
> > I'm not sure where we are in getting CRAN packages getting their
>
Hi,
I'm not sure where we are in getting CRAN packages getting their
_R_CHECK_LENGTH_1_LOGIC2_=true bugs fixed (*), but maybe it'd help to
make _R_CHECK_LENGTH_1_LOGIC2_=warn the new default in the upcoming R
3.6.2? Warnings of type:
$ R --vanilla
> Sys.setenv("_R_CHECK_LENGTH_1_LOGIC2_" = "warn"
$ R --vanilla
R version 3.6.1 (2019-07-05) -- "Action of the Toes"
Copyright (C) 2019 The R Foundation for Statistical Computing
Platform: x86_64-pc-linux-gnu (64-bit)
...
> str(base::`+`)
function (e1, e2)
> plus <- structure(base::`+`, class = "plus")
> str(plus)
function (e1, e2)
- attr(*, "c
Yes, I ran into this too. I think they fixed it for RStudio 1.3
(https://github.com/rstudio/rstudio/pull/5457/files). My workaround
is to enable these checks conditionally on not running R in the
RStudio Console (it works in the RStudio Terminal). To test for the
RStudio Console, you need to turn
1 - 100 of 916 matches
Mail list logo
