similar to: href and Rd

Hi all, Sorry if this doesn't end up in the thread. Tobias Verbeke forwarded that e-mail to me, because he thought I would be interested in maintaining the Programming Tools CTV. I wasn't subscribed to R-devel yet, but I would indeed like to volunteer to maintain the Programming Tools CTV. It will be my first time creating a CTV, so some guidance on getting it setup will be appreciated.

I have found a strange "ifelse" behaviour (I think) This works: > ifelse(T,1+1,1+2) [1] 2 > ifelse(F,1+1,1+2) [1] 3 Maybe I missed something about R internals, but why > ifelse(T,print("hello"),print("goodbye")) [1] "hello" [1] "hello" > ifelse(F,print("hello"),print("goodbye")) [1] "goodbye" [1]

Dear Willem, Personally, I use the R-forge project for the distribution CTV : https://r-forge.r-project.org/projects/ctv/ It?s an alternative option to github. Regards, Christophe --------------------------------------- Christophe Dutang LMM, UdM, Le Mans, France web: http://dutangc.free.fr Le 23 janv. 2015 ? 12:49, Luca Braglia <lbraglia at gmail.com> a ?crit : > Hi Willem >

Hi read.table in a table with numb of read elements not multiple of columns Avviso in scan(file, what, nmax, sep, dec, quote, skip, nlines, na.strings, : il numero di elemtni letti non ?? un multiplo del numero di colonne --> change "elemtni" to "elementi" Regards Luca

On Thu, Jan 22, 2015 at 12:45 PM, Achim Zeileis <Achim.Zeileis at uibk.ac.at> wrote: > On Thu, 22 Jan 2015, Max Kuhn wrote: > >> I've had a lot of requests for additions to the reproducible research >> task view that fall into a grey area (to me at least). >> >> For example, roxygen2 is a tool that broadly enable reproducibility >> but I see it more as

I've had a lot of requests for additions to the reproducible research task view that fall into a grey area (to me at least). For example, roxygen2 is a tool that broadly enable reproducibility but I see it more as a tool for better programming. I'm about to check in a new version of the task view that includes packrat and checkpoint, as they seem closer to reproducible research, but also

Hi few typos i've found ?.C Specifying 'ENCODING' overrrides any declared encodings (see 'link{Encoding}') \link{Encoding} -------------------- writing R extensions, pag 73 (pdf version), note 1, and we provided an emulation on Windows 2000): see ?dyn.oad ^ ^^ 1

Full_Name: Luca Braglia Version: 2.8 OS: Windows Submission from: (NULL) (85.18.136.110) >From ?as.POSIXct ## SPSS dates (R-help 2006-02-17) z <- c(10485849600, 10477641600, 10561104000, 10562745600) as.Date(as.POSIXct(z, origin="1582-10-14", tz="GMT")) ^^ It should be 15 (Gregorian calendar adoption day, when

Dear all, can you reproduce (on testing or unstable, especially) this 2 line error which inhibits interactive graphics (to me, tested on 2 debian testing boxes). l at m740n:~$ R --vanilla > example(hist) hist> op <- par(mfrow = c(2, 2)) Error in (function (display = "", width, height, pointsize, gamma, bg, : il modulo X11 non pu? essere caricato Inoltre: Warning message:

On Thu, Jan 22, 2015 at 1:05 PM, Achim Zeileis <Achim.Zeileis at uibk.ac.at> wrote: > On Thu, 22 Jan 2015, Max Kuhn wrote: > >> On Thu, Jan 22, 2015 at 12:45 PM, Achim Zeileis >> <Achim.Zeileis at uibk.ac.at> wrote: >>> >>> On Thu, 22 Jan 2015, Max Kuhn wrote: >>> >>>> I've had a lot of requests for additions to the

Hi, I have a trouble trying to use \href in a rd doc. See example below: \references{ \href{http://www.ncbi.nlm.nih.gov/pmc/articles/PMC2702787/}{Vaniscotte A., Pleydell D., Raoul F., Quere J.P., Coeurdassier M., Delattre P., Li T., Qian W., Takahashi K., Weidmann J.C., Qiu J., Giraudoux P. 2009 Modelling and spatial discrimination of small mammal assemblages: an example from western

Hello R-users I have a situation like this x=c(1,3,2) y=data.frame("a"=1:3, "b"=4:6, "c"=7:9)*2 So we have > t(t(x)) [,1] [1,] 1 [2,] 3 [3,] 2 And > y a b c 1 2 8 14 2 4 10 16 3 6 12 18 I would like to obtain a vector with number taken from the data.frame: x is needed as row index With c(1,3,2), in this case the ouput should be 2 16

I don't have an opinion on the URL shorteners, but how about the original question? Redirection can be extremely useful in general. Shortening URLs is only one of its possible applications. FWIW, CRAN uses (303) redirect itself, e.g., https://cran.r-project.org/package=MASS is redirected to https://cran.r-project.org/web/packages/MASS/index.html Should these "canonical" CRAN links be

Hello * I would like to reshape wide the following dataset: > rl <- read.dta("intermedi/rapporti_lavoro.dta") [c("id_rl","prog","sil_pi","sil_cf","sil_dat_avv")] > dim(rl) [1] 12964 5 > object.size(rl) 1194728 bytes > head(rl) id_rl prog sil_pi sil_cf sil_dat_avv 1 638 1 04567XXXXXX

Bug or feature? I get the following error from parse_Rd() when a user Rd macro (including system ones) is invoked with empty argument {}, eg \mymacro{}: Error in tools::parse_Rd(fn) : Value of SET_STRING_ELT() must be a 'CHARSXP' not a 'NULL' A full example is further below with the system macro \CRANpkg{}. In this example it doesn't make sense to use empty argument but

hello everybody i was seeking a converter beetween R regression output (eg with summary) and the conventional way to present regression output in paper: every model as a vertical vector with \beta, t beetween parenthesis below the first, and other statistics (R^2 etc) . I've seen hmisc and xtable, and if I didn't miss something, they don't include something like that. Thank you

Hello * i have to rename a lot of variables, and, given that they have regular name constructs, I would like to use regexps. Here's a dump of my head(names(df)) varnames <- c("id.quest", "txt.1.3", "col1.1.3", "col2.1.3", "col3.1.3", "col4.1.3", "col5.1.3", "txt.2.3", "col1.2.3",

hello everybody solved the problem with summary, now I have another one eg I estimate > try.op <- polr( > as.ordered(sod.sit.ec.fam) ~ > log(y) + > log(1 + nfiglimin) + > log(1 + nfiglimagg) + > log(ncomp - nfiglitot) + > eta + > I(eta^2) + >

On 16/09/2020 4:51 p.m., Simon Urbanek wrote: > I can't comment for CRAN, but generally, shorteners are considered security risk so regardless of the 301 handling I think flagging those is a good idea. Also I think it is particularly bad to use them in manuals because it hides the target so the user has no idea what hey will get. I agree, and we do have \href{}{} in Rd files and similar in

While on the topic of Rd macro arguments, it seems that if a multiline argument is supplied, the lines after the first are silently ignored: f <- tempfile() mac6 <- "\\newcommand{\\mac6}{mac6: #1}" cat(mac6, "\\mac6{2*3 2+2 sin(pi) }\n", file = f) rd <- tools::parse_Rd(f) > rd mac6: 2*3 --- Georgi Boshnakov -----Original Message----- From: Tomas Kalibera