Re: [Rd] Cases of TAB-completion that hang Rterm
On Tue, Jun 7, 2011 at 1:49 PM, Henrik Bengtsson h...@biostat.ucsf.edu wrote:
FYI,
via a bug report of one of my packages, I discovered that the
following cases will hang Rterm when using TAB completion:
CASE #1:
Adding an empty default function for tail() causes Rterm on Windows to
hang if one press TAB at the prompt:
% Rterm -vanilla
tail.default - function(...) {}
[PRESS TAB]
Error in specialOpLocs(text) :
(list) object cannot be coerced to type 'double'
After this Rterm becomes completely unresponsive. The same error
message will show up with Rgui, but R remains responsive.
CASE #2:
While troubleshooting the above, I discovered that if one does:
debug(utils:::.guessTokenFromLine)
[PRESS TAB]
or
debug(utils:::.win32consoleCompletion)
[PRESS TAB]
then Rterm hangs too (not Rgui).
This happens with R v2.13.0 patched (2011-05-30 r56020) and R v2.14.0
devel (2011-05-30 r56020) on Windows.
This should now be fixed in both r-devel (for a few days now) and r-patched.
-Deepayan
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] [Rcpp-devel] Error using RcppGSL
Hi, It is on windows XP. I did not install GSL yet, which version should I install from http://gnuwin32.sourceforge.net/packages/gsl.htm? I want to use RcppGSL via the inline package. Thanks, Oyvind From: Dirk Eddelbuettel e...@debian.org To: Douglas Bates ba...@stat.wisc.edu Cc: oyvfos oyv...@yahoo.no; r-devel@r-project.org; rcpp-devel rcpp-de...@r-forge.wu-wien.ac.at Sent: Wed, June 22, 2011 1:12:13 AM Subject: Re: [Rcpp-devel] [Rd] Error using RcppGSL On 21 June 2011 at 09:50, Douglas Bates wrote: | Questions like this would get a faster response on the Rcpp-devel list, to | which I am copying this reply. Quite right. Dropping r-devel now. You need to subscribe to rcpp-devel if you want to post there. | On Jun 21, 2011 6:35 AM, oyvfos oyv...@yahoo.no wrote: | Hi, I get an error using RcppGSL: fatal error: gsl/gsl_vector.h:No such file | or directory. What is the best way to install these files as they seem to | be missing? What platform, ie what operating system? Do you have GSL installed? Including development headers and libraries? Did you _ever_ compile anything against GSL? Dirk | Thanks, | Oyvind | | | -- | View this message in context: http://r.789695.n4.nabble.com/ | Error-using-RcppGSL-tp3613535p3613535.html | Sent from the R devel mailing list archive at Nabble.com. | | __ | R-devel@r-project.org mailing list | https://stat.ethz.ch/mailman/listinfo/r-devel | | -- | ___ | Rcpp-devel mailing list | rcpp-de...@lists.r-forge.r-project.org | https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel -- Gauss once played himself in a zero-sum game and won $50. -- #11 at http://www.gaussfacts.com [[alternative HTML version deleted]] __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] Controlling stdin and stdout in an embedded R instance
Thank you, this example helped. Mike Sonsini On 6/17/2011 10:29 AM, Simon Urbanek wrote: Mike, there are many examples of embedding R, one of them is rJava/JRI and you can see how to initialize R with custom callbacks at http://svn.rforge.net/org/trunk/rosuda/JRI/src/Rinit.c Cheers, Simon __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
[Rd] Checking R manual build
Is there a quick way of checking the R manuals built from the .texi files in
../doc/manual without building the rest of R?
Going from a vanilla checkout, some included files are missing (eg
version.texi) and created by the makefiles, so it looks like the complete make
script needs to be run at least once ... and then one has a number of
make-generated changes to one's R sources to worry about in any subsequent
diff.
Is the only route to export the svn copy, build from the exported copy and then
use texinfo to check the manual pages using the make-built includes and rules?
Steve Ellison
***
This email and any attachments are confidential. Any use...{{dropped:8}}
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
[Rd] First package submission to CRAN
I'm preparing to submit my first package to CRAN, thanks to the help of too many people to mention. I've built and checked the package on Windows ( making a zip) and my path points to the 64 bit version of R. Everything builds and checks and the final warnings have been fixed. My package is pure R with no source from other languages. My questions are as follows. I've read the docs and just need a bit of clarification. 1. For submission I should just build source R CMD build mypkg which outputs a tar.gz 2. Do I have to/ how do I build for 32 bit? Thanks, Steve [[alternative HTML version deleted]] __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] First package submission to CRAN
Hi, By default, R CMD build makes sources, you have to use --binary if you want to get binaries. But you have to submit sources to the CRAN ftp server (and not binary). So just run a R CMD build. C -- Christophe Dutang Ph.D. student at ISFA, Lyon, France website: http://dutangc.free.fr Le 22 juin 2011 à 22:12, steven mosher a écrit : I'm preparing to submit my first package to CRAN, thanks to the help of too many people to mention. I've built and checked the package on Windows ( making a zip) and my path points to the 64 bit version of R. Everything builds and checks and the final warnings have been fixed. My package is pure R with no source from other languages. My questions are as follows. I've read the docs and just need a bit of clarification. 1. For submission I should just build source R CMD build mypkg which outputs a tar.gz 2. Do I have to/ how do I build for 32 bit? Thanks, Steve [[alternative HTML version deleted]] __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] First package submission to CRAN
On 23/06/11 08:34, Christophe Dutang wrote: Hi, By default, R CMD build makes sources, you have to use --binary if you want to get binaries. But you have to submit sources to the CRAN ftp server (and not binary). So just run a R CMD build. C -- Christophe Dutang Ph.D. student at ISFA, Lyon, France website: http://dutangc.free.fr That is now deprecated Christophe. Recommended now is R CMD INSTALL --build to get a binary. See the recent thread with the subject Porting unmaintained packages to post R 2.10.0 era David Scott Le 22 juin 2011 à 22:12, steven mosher a écrit : I'm preparing to submit my first package to CRAN, thanks to the help of too many people to mention. I've built and checked the package on Windows ( making a zip) and my path points to the 64 bit version of R. Everything builds and checks and the final warnings have been fixed. My package is pure R with no source from other languages. My questions are as follows. I've read the docs and just need a bit of clarification. 1. For submission I should just build source R CMD build mypkg which outputs a tar.gz 2. Do I have to/ how do I build for 32 bit? Thanks, Steve [[alternative HTML version deleted]] __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel -- _ David Scott Department of Statistics The University of Auckland, PB 92019 Auckland 1142,NEW ZEALAND Phone: +64 9 923 5055, or +64 9 373 7599 ext 85055 Email: d.sc...@auckland.ac.nz, Fax: +64 9 373 7018 __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
[Rd] suggestion for subset.data.frame()
Hello,
Currently, subset.data.frame() does
if (missing(subset))
r - TRUE
else {
perhaps better might be:
if (missing(subset))
r - rep(TRUE, nrow(x))
else {
The rationale being, if 'x' has zero rows and 'subset' is missing, we
don't want to end up with more rows than we started with:
subset(head(iris, 0), select = -Species)
Sepal.Length Sepal.Width Petal.Length Petal.Width
NA NA NA NA NA
Thoughts?
-Ben
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] Checking R manual build
On Wed, 22 Jun 2011, Stephen Ellison wrote: Is there a quick way of checking the R manuals built from the .texi files in ../doc/manual without building the rest of R? What does 'check' mean? Going from a vanilla checkout, some included files are missing (eg version.texi) and created by the makefiles, so it looks like the complete make script needs to be run at least once ... and then one has a number of make-generated changes to one's R sources to worry about in any subsequent diff. You haven't told us your OS (pace the posting guide). On all systems the first step is to run configure (but that has already been done for you on Windows, but you do need to create MkRules from MkRules.local). Again except on Windows, we recommend working in a build directory other than the sources. Even on Windows there will be *no* 'make-generated changes to one's R sources': no files are changed but some are generated. make distclean will clean up .. Is the only route to export the svn copy, build from the exported copy and then use texinfo to check the manual pages using the make-built includes and rules? Possibly, depending on the meaning of 'check'. R-core (as the only people changing these manuals) also need to use a pdflatex system, to check that the PDF version can be made as the manuals have PDF-specific (and HTML-specific) sections. -- Brian D. Ripley, rip...@stats.ox.ac.uk Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/ University of Oxford, Tel: +44 1865 272861 (self) 1 South Parks Road, +44 1865 272866 (PA) Oxford OX1 3TG, UKFax: +44 1865 272595 __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
