similar to: [Rd] source(echo = TRUE) with a iso-8859-1 encoded file gives an error

On Fri, May 4, 2018 at 4:47 PM, Scott Kostyshak <skostyshak at ufl.edu> wrote: > I have very little knowledge about file encodings and would like to > learn more. > > I've read the following pages to learn more: > > http://stat.ethz.ch/R-manual/R-devel/library/base/html/Encoding.html >

I have very little knowledge about file encodings and would like to learn more. I've read the following pages to learn more:

Hi Scott, This question is appropriate for the r-help mailing list, but probably off-topic here on r-devel. Best, Ista On Tue, May 1, 2018 at 2:57 PM, Scott Kostyshak <skostyshak at ufl.edu> wrote: > I have very little knowledge about file encodings and would like to > learn more. > > I've read the following pages to learn more: > >

The attached patch adds some sanity checks to the "type" argument of quantile(). Output from the following commands show the change of behavior with the current patch: vec <- 1:10 quantile(vec, type = c(1, 2)) quantile(vec, type = 10) quantile(vec, type = "aaa") quantile(vec, type = NA_real_) quantile(vec, type = 4.3) quantile(vec, type = -1) Current behavior

I wonder if it would be helpful to mention in ?stopifnot that stopifnot(logical(0)) does not give an error (for background on why this is the case, see [1]). For example, ?all explicitly mentions the following: That all(logical(0)) is true is a useful convention and includes an example: all(logical(0)) # true, as all zero of the elements are true. I think it would be nice to give examples

Is there a way to mark a ticket as a potential regression in the bug tracker? I think the following issue is a regression: https://bugs.r-project.org/bugzilla/show_bug.cgi?id=17684 I've just tested (2020-06-12 r78687) and what I believe to be a regression is still there. I don't think the bug has bitten many people, so I don't think it is critical, but often it is helpful to mark

On 04/01/2020 4:35 p.m., Scott Kostyshak wrote: > On Fri, May 31, 2019 at 01:28:55AM -0400, Scott Kostyshak wrote: >> The attached patch adds some sanity checks to the "type" argument of ... > Bump. For this type of patch proposal, is it better to use the > bug tracker? For almost any patch proposal it is. Certainly if you don't get action (or at least discussion)

>>>>> Jan van der Laan <rhelp at eoos.dds.nl> >>>>> on Fri, 6 Oct 2017 12:13:39 +0200 writes: > It is actually model.matrix that crashes, not glm. Same > crash occurs with e.g. lm. > model.matrix(dob_mon ~ dob_day*dob_mon, data = tab) > also crashes R. Yes, segmentation fault. It only happens when these are *logical*

Hevr? told me that people from Bioconductor and possibly others are keeping an eye on this thread so it would be good to post a note here too. As of version 4.0.0, the official R for Windows and binary packages provided via CRAN are built with gcc-8.3.0 from rtools40, as shown in the CRAN check table: https://cran.r-project.org/web/checks/check_flavors.html Instructions and installers for

Hi, I would like to learn the details regarding what exactly PGO does for basic block layout/code placement optimizations in llvm. Could you please point me to some descriptions? Is it close to this paper (Karl Pettis and Robert C. Hansen. 1990. Profile guided code positioning. PLDI'90) http://perso.ensta-paristech.fr/~bmonsuez/Cours/B6-4/Articles/papers15.pdf? Whether it is purely

So for auth_policy_server_api_header. is the value of our_password come from the hashed response or the plain-text password? What else am I doing wrong? Mar 7 09:20:53 olddsm wforce[17763]: WforceWebserver: HTTP Request "/" from 127.0.0.1:56416: Web Authentication failed curl -X POST -H "Content-Type: application/json" --data '{"login?:?ouruser?, "remote":

Huge thanks to you (Jeroen) and R-core for doing this. I wasn't involved with this directly but I know it was a pretty seriously heavy list so well done all around! ~G On Tue, Apr 28, 2020, 11:04 AM Herv? Pag?s <hpages at fredhutch.org> wrote: > Thanks Jeroen! > > > On Tue, Apr 7, 2020 at 6:07 PM Kevin Ushey <kevinushey at gmail.com> wrote: > >> >

On Fri, May 31, 2019 at 01:28:55AM -0400, Scott Kostyshak wrote: > The attached patch adds some sanity checks to the "type" argument of > quantile(). Output from the following commands show the change of > behavior with the current patch: > > vec <- 1:10 > quantile(vec, type = c(1, 2)) > quantile(vec, type = 10) > quantile(vec, type = "aaa")

I’m happy to run them, although I’d appreciate a pointer to the appropriate documentation. From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Tobias Hieta via llvm-dev <llvm-dev at lists.llvm.org> Reply-To: Tobias Hieta <tobias at plexapp.com> Date: Wednesday, September 30, 2020 at 11:15 AM To: Hans Wennborg <hans at chromium.org> Cc: llvm-dev <llvm-dev at

Thanks Jeff, So I initially when I got the computer moved my old packages into the new directory rather than downloading and installing them again. That was fine. I then just did a test to see if I could write in the folder and indeed I can. Just not via R. I uninstalled R Open, installed R 3.4.4, and the problem persisted, including just running it from the R console rather than from R

On Fri, Mar 23, 2018 at 6:43 PM, Rui Barradas <ruipbarradas at sapo.pt> wrote: > Hello, > > Not exactly an answer but here it goes. > If you use the formula interface the names will be retained. Also if you pass named arguments: aggregate(iris["Sepal.Length"], by = iris["Species"], FUN = foo) # Species Sepal.Length # 1 setosa 5.006 # 2

Thanks, Here's the error, for example: > install.packages("mgcv") Installing package into 'C:/Users/pl39/Documents/R/win-library/3.4' (as 'lib' is unspecified) trying URL 'https://mirrors.nics.utk.edu/cran/bin/windows/contrib/3.4/mgcv_1.8-23.zip' Content type 'application/zip' length 2775362 bytes (2.6 MB) downloaded 2.6 MB package 'mgcv'

A) Don't try to "move" packages from one library (=directory of installed packages) to another. B) Although R Open is very close to CRAN R, it has some differences that you REALLY NEED TO READ about at their website. Pay particular attention to the checkpoint feature in this case. Note that troubles installing it or with the MKL are probably off-topic here, though R language

Ok, thanks -- > sessionInfo() R version 3.4.4 (2018-03-15) Platform: x86_64-w64-mingw32/x64 (64-bit) Running under: Windows >= 8 x64 (build 9200) Matrix products: default locale: [1] LC_COLLATE=English_United States.1252 LC_CTYPE=English_United States.1252 [3] LC_MONETARY=English_United States.1252 LC_NUMERIC=C [5] LC_TIME=English_United States.1252

I recently debugged an issue where I wasn't getting stack traces from ASAN on 32-bit ARM (on Android) when using a libclang_rt.asan-arm-android.so I'd built myself. I finally ended up tracing it to a build issue; the CMake build check for -funwind-tables was failing (because of some missing link libraries), so compiler-rt wasn't being built with that flag, which in turn led to all