similar to: Rd files

I am stumped in determining the proper syntax for including displayed S code within an R .Rd documentation file, in places other than \examples{}. I have tried \code{ line 1 line 2 } but the lines get run together. When I terminate the lines by \cr, the "\cr" actually appears in the resulting html file. This is all inside a customized \section{}. On a related note, what is

Dear R-devel, I'm working on Prof. Loader's new version of locfit to try to get it pass R CMD check. I'm almost there, but I have a problem with some Rd files that I hope some one can help me resolve. Here's an example: In the package there's a function called locfit.censor(). This function can be used in a few different ways: locfit.censor(x, y, cens, ...)

The problem is the following # make docs Make: Don't know how to make ../src/library/*/man/*.Rd. Stop. *** Exit 1 (ignored) # I am using a DEC alpha 200/4/233 with Digital Unix 3.2D My previous version of R was R-0.50-a1. I have installed around 3 or 4 previous versions on the same system and never had a problem (but, then the Makefile was very different). The first make to compile

The problem is the following # make docs Make: Don't know how to make ../src/library/*/man/*.Rd. Stop. *** Exit 1 (ignored) # I am using a DEC alpha 200/4/233 with Digital Unix 3.2D My previous version of R was R-0.50-a1. I have installed around 3 or 4 previous versions on the same system and never had a problem (but, then the Makefile was very different). The first make to compile

[this message bounced, because it had 'help' at beginning of Subject. Now sent as "approved". -- MM] I'm not happy at all with the html and latex version of the base help files, because presenting (currently) 320 files in alphabetic order is not a good way for unexperienced users. I'm thinking about introducing a new command like \category or whatever to split the

Version: platform = sparc-sun-solaris2.6 arch = sparc os = solaris2.6 system = sparc, solaris2.6 status = status.rev = 0 major = 0 minor = 64.2 year = 1999 month = July day = 3 language = R -- It is unclear to me that the handling of NAs is desirable, and it has problems with names: > z <- c(T,T,NA,F,T) > names(z) <- letters[1:5] > which(z) Error: names attribute

Hi, I recently compiled 1.6 on NT4 but I am having a problem with Sweave. Using the inbuilt 'Sweave-test-1.Rnw' file as an example: ------- > library(tools) > testfile <- file.path(.path.package("tools"), "Sweave", "Sweave-test-1.Rnw") ## create a LaTeX file Sweave(testfile) testfile <-

Hi All, It seems that the question of how may people use (or download) R, and it's packages is one that comes up on a fairly regular basis in a variety of forums (There was also recent thread on the subject on Stack Overflow). A couple of students at UCLA (including myself), wanted to address the issue, so we set up a system to get and parse the cran.stat.ucla.edu APACHE logs every night, and

Thanks to Peter Dalgaard's message, I learned a bit more about the 'par' function and rewrote my HTML help file accordingly. Is it appropriate to submit such changes somewhere to improve the documentation? I would also be willing to write some missing documentation as well. Dr. Jim Lemon -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing

On Mon, Jul 28, 2014 at 12:18:10PM -0700, H. Peter Anvin wrote: > On 07/28/2014 12:04 PM, Eduardo Habkost wrote: > > When CONFIG_PARAVIRT is enabled, the kernel is ignoring exceptions on > > the {rd,wr}msr instructions. This makes serious issues (either on the > > guest kernel, or on the host) be silently ignored, and is different from > > the native MSR code (which does

On Mon, Jul 28, 2014 at 12:18:10PM -0700, H. Peter Anvin wrote: > On 07/28/2014 12:04 PM, Eduardo Habkost wrote: > > When CONFIG_PARAVIRT is enabled, the kernel is ignoring exceptions on > > the {rd,wr}msr instructions. This makes serious issues (either on the > > guest kernel, or on the host) be silently ignored, and is different from > > the native MSR code (which does

When CONFIG_PARAVIRT is enabled, the kernel is ignoring exceptions on the {rd,wr}msr instructions. This makes serious issues (either on the guest kernel, or on the host) be silently ignored, and is different from the native MSR code (which does not ignore the exceptions). As paravirt.h already includes linux/bug.h, I don't see what was the original issue preventing BUG_ON from being used.

When CONFIG_PARAVIRT is enabled, the kernel is ignoring exceptions on the {rd,wr}msr instructions. This makes serious issues (either on the guest kernel, or on the host) be silently ignored, and is different from the native MSR code (which does not ignore the exceptions). As paravirt.h already includes linux/bug.h, I don't see what was the original issue preventing BUG_ON from being used.

At the Vienna meeting we discussed the problems encountered on some operating systems when storing many small files in a directory. In particular the directories $RHOME/library/base/help/, $RHOME/library/base/R-ex/, and $RHOME/library/base/data/ can take up an enormous amount of storage on the Macintosh or on Windows systems because the minimum amount of storage per distinct file is quite large.

Hi, here's a short summary of all the mails I got concerning the R help system during the last days ... I really want to have all open questions in this list, so if I forgot your most important topic please forgive (and remind me again) ... it's probably only because of lack of time such that I had to compile the list in a hurry ... Ok, here we go: 1) It would be useful to have a button

Hi, I just had a very quick look at the StatDataML proposal --- nice work! At the risk of showing my ignorance, I want to mention my first impressions. My first impression is that defining datasets in terms of arrays and list is a bit too high a level. What about simpler vectors, scalars? (I know that R/S don't have scalars, but other systems/applications do.) Can we think of a core

Dear R experts--- after many years, I am planning to give in and write my first R package. I want to combine my collection of collected useful utility routines. as my guide, I am planning to use Friedrich Leisch's "Creating R Packages: A Tutorial" from Sep 2009. Is there a newer or better tutorial? this one is 4 years old. I also plan on one change---given that the

I am using R 1.2.3 on Linux Mandrake 7.2. I have a ton of S Nroff help files that end with source code typified by the following: Last S statement in an example, e.g. X <- y ..KW models ..KW regression ..WR When using R RMD Sd2Rd to create the .Rd file I get X <- y \keyword{models} \keyword{regression} } The } matches a { in \examples{ at the beginning of the example code (started in

>>>>> On Sun, 27 Aug 2006 07:45:00 -0700, >>>>> Martin Morgan (MM) wrote: > [A build system misconfiguration at Bioconductor lead to a discussion > about whether \usepackage{Sweave} should be included in .Rnw > documents. Leaving this line out causes a problem on Windows, as > indicated below.] > I think the problem is '~', which

Dear R-developers, I am trying to reproduce the autoconf.ac example from R-ext and fail. My autoconf file looks like this [autoconf.ac] # original by Friedrich Leisch, much changed by BDR AC_INIT([SBMLodeSolveR]) dnl Select an optional include path, from a configure option dnl or from an environment variable. AC_ARG_WITH([sbmlode-include],