similar to: Comments not documented in language reference (PR#2367)

Displaying 20 results from an estimated 10000 matches similar to: "Comments not documented in language reference (PR#2367)"

2011 Feb 13
1
RCytoscape setPosition error
Hi Can some one please point out where i am wrong. I am trying to position set of nodes column-wise in cytoscape using RCytoscape A----D B----E C----F ------------------- g <- new ('graphNEL', edgemode='undirected') cw <- CytoscapeWindow ('smallExample', graph=RCytoscape::makeSimpleGraph()) layout (cw, 'jgraph-spring') redraw(cw) nodesFr = c('A',
2005 Oct 11
2
Sweave and Rnews
Hello list, I am writing a paper for Rnews. I use Sweave to do it. I did not find information about writing a paper for Rnews using Sweave and have some questions: - Is there a problem to use the environment 'Sinput' in the place of 'example' or 'smallexample'. It works fine but perhaps there are some technical/editorial problems ? - I have some long lines of code in
2004 Oct 10
1
An introduction to R - language is R or S ?
I have done a diff between R 2.0 and R 1.9 versions of 'An introduction to R'. I notice that line 196 of R-intro.texi now calls the language used in R 'S', and not 'R' any longer. I imagine there must be a reason for this, it is not a simple mistake is it ? -- Michele Alzetta
2005 Nov 18
1
R-exts.texi in SVN version 36380
G'day all, after issuing `svn up' on my machine this morning, I noticed that `make info' choked on R-exts.texi. Below is a patch that seems to solve the problem. BTW, while `make info' runs now, I still get the following warning: /usr/bin/makeinfo --enable-encoding -D UseExternalXrefs -I/opt/src/R-devel-src/doc/manual /opt/src/R-devel-src/doc/manual/R-exts.texi
2003 Jul 15
2
How to do get verbatim in Rd files
I want to include a multi-line code block in the details section of a R manual page. How do I get an appropriate verbatim-like environment? \verbatim{...} doesn't do the trick, neither does \code{...}. -Greg LEGAL NOTICE\ Unless expressly stated otherwise, this messag...{{dropped}}
2015 Sep 07
2
Build rpm package for R-MKL
I want to create a clean .rpm package for R built with MKL and ICC. I follow Fedora instrcutions[0] to create the package. As a base, I use the R-3.2.2.src.rpm. I am left with this error: ------------------------------------------ installing R info pages ... updating '/usr/share/info/dir' ... make[1]: Leaving directory '/home/poisonivy/rpmbuild/BUILD/R-3.2.2/doc/manual' + mv
2003 Jul 21
2
missing permissions in reference manual copyright page (PR#3528)
Hi, I noticed that the R reference manual seems to be missing the license permissions on the copyright page. Below is a patch to "refman.top" which adds the same permissions as the @permission{} macro in "R-defs.texi". I'm filing this bug as I have been preparing to publish the R Reference Manual (in several volumes). I plan to donate 5 EUR to the R-foundation for each
2005 May 14
2
[LLVMdev] Cygwin llvm-gcc build error
Now I believe that I am getting the same error as I was getting last time I tried to build llvm-gcc. It may possibly be my Cygwin instillation but am not sure. makeinfo --split-size=5000000 -I ../../../src/llvm-gcc/gcc/doc -I ../../../src/ llvm-gcc/gcc/doc/include \ -o ../../../src/llvm-gcc/gcc/doc/cpp.info ../../../src/llvm-gcc/gcc/doc/cpp.texi ' in
2015 Sep 09
2
Build R form source - manuals
I built R form source succesfully on my Fedora 22 box. No errors. I can read there is an issue with some manuals at build time when running makeinfo, especially these two: doc/manual/R-exts.texi cp doc/manual/R-intro.texi Some distro have hacks about makeinfo 5 in their build script. I wonder if some manuals are broken but couldn't see it when running make. May someone tells me more about
2005 May 17
0
[LLVMdev] Cygwin llvm-gcc build error
Hi Aaron, have you got any help on this? Henrik >From: "Aaron Gray" Date: Sat, 14 May 2005 18:26:01 +0100 > >Now I believe that I am getting the same error as I was getting last time I >tried to build llvm-gcc. >It may possibly be my Cygwin instillation but am not sure. > > >makeinfo --split-size=5000000 -I ../../../src/llvm-gcc/gcc/doc -I >../../../src/
2005 May 17
2
[LLVMdev] Cygwin llvm-gcc build error
>Hi Aaron, >have you got any help on this? Henrik, No. This is where I was stuck some months ago. I do not know makeinfo so was not able to proceed any thurther than verifying the makeinfo statement did the same thing when done on the command line. Basically I am stuck. I do not know whether it was my Cygwin configuration or something I have done or not done or whether it is a valid
2004 Nov 16
1
[LLVMdev] Makeinfo fails
Hi, Is it really true that nobody isn't able to give me a clue why makeinfo fails with this error: doc/cpp.texi:50: Unknown index `vr' and/or `op' in @synindex. ------------------------- make[2]: Entering directory `/C/Projects/src/llvm-gcc/gcc' for d in libgcc; do \ if [ -d $d ]; then true; else /bin/sh ./mkinstalldirs $d; fi; \ done if [ -f stmp-dirs ]; then true; else
2013 May 28
3
perl 5.18
I guess perl 5.18 was released and it is causing issues texi2html -monolithic -number-sections qemu-doc.texi texi2html -monolithic -number-sections qemu-tech.texi /data/dev/xen/xen-4.3-git/src/xen-build/tools/qemu-xen-traditional-dir/ texi2pod.pl qemu-doc.texi qemu.pod pod2man --section=1 --center=" " --release=" " qemu.pod > qemu.1 qemu.pod around line 91: Non-ASCII
2013 May 28
3
perl 5.18
I guess perl 5.18 was released and it is causing issues texi2html -monolithic -number-sections qemu-doc.texi texi2html -monolithic -number-sections qemu-tech.texi /data/dev/xen/xen-4.3-git/src/xen-build/tools/qemu-xen-traditional-dir/ texi2pod.pl qemu-doc.texi qemu.pod pod2man --section=1 --center=" " --release=" " qemu.pod > qemu.1 qemu.pod around line 91: Non-ASCII
2005 May 14
0
[LLVMdev] Cygwin LLVM Install Errors
I can't reproduce these on GNU-Linux/x86. What platform are you on? Reid. On Sat, 2005-05-14 at 16:50 +0100, Aaron Gray wrote: > AFAICT these are valid errors. > > Getting an error on the 'make install' for LLVM :- > > > make[2]: Entering directory `/usr/build/llvm/tools/llvm-ar' > llvm[2]: Installing Debug /usr/llvm/bin/llvm-ar > /usr/bin/install:
2014 Feb 04
1
[PATCH] nouveau/codegen: allow tex offsets on non-TXF instructions (e.g. TXL)
Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- This fixes the bin/fs-textureOffset-2D piglit test on nv50. Have yet to re-run the full piglit suite with this change in place, but it seems pretty obvious. src/gallium/drivers/nouveau/codegen/nv50_ir_from_tgsi.cpp | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/src/gallium/drivers/nouveau/codegen/nv50_ir_from_tgsi.cpp
2005 May 14
4
[LLVMdev] Cygwin LLVM Install Errors
AFAICT these are valid errors. Getting an error on the 'make install' for LLVM :- make[2]: Entering directory `/usr/build/llvm/tools/llvm-ar' llvm[2]: Installing Debug /usr/llvm/bin/llvm-ar /usr/bin/install: target `/usr/llvm/bin/llvm-ar' is not a directory make[2]: *** [/usr/llvm/bin/llvm-ar] Error 1 make[2]: Leaving directory `/usr/build/llvm/tools/llvm-ar' make[1]: ***
2007 Aug 31
1
compiling R-devel
Hello. I am in a habit of compiling daily snapshots of R-devel and R-patched on my Windows XP workstation. I have cygwin environment with up-to-date RTools and MiKTeX. I run cygwin and MiKTeX upadaters pretty often (every couple of days) so both of them are reasonably current. Recently I noticed a small annoyance when compiling R-dvel. It started happening right after I updated to the new
2010 Jan 13
4
merging issue.........
hi, I have a question about merging two files. For example, I have two files, the first file is like the following: id trait1 1 10.2 2 11.1 3 9.7 6 10.2 7 8.9 10 9.7 11 10.2 The second file is like the following: id trait2 1 9.8 2 10.8 4 7.8 5 9.8 6 10.1 12 10.2 13 10.1 now I want to merge the two files by the variable "id", I only want
2008 Jun 23
1
r-base build: failure to convert R-FAQ to pdf
We have received an email in Ubuntu alerting us that something strange was going on during the r-base 2.7.1 rc build (see [1]). It seems that there is an error during the convertion of R-FAQ.texi to pdf. The following excerpt, taken from [2], shows the problem: /bin/sh: line 0: test: too many arguments TEXINPUTS=".:$TEXINPUTS" /usr/bin/texi2dvi --texinfo="@set UseExternalXrefs