headers
Dale.W.Steele | 1 Feb 2011 01:26
Picon

Re: Finding Rterm in R 2.12.0 on Windows

I've installed the most recent version of ESS from subversion. ESS now  
finds both the 32-bit and 64-bit installed versions of R-patched on my  
64-bit Windows 7 system.

One interesting issue. If I open an empty file test.R and navigate via the  
ESS menu, Ie. "Start Process:Other and select the 64 bit version, then the  
following text appears in the buffer:

"ESS [S(R): C:/Program Files/R/R-2.12.1patched/bin/i386/Rterm.exe] starting  
data directory?"

Although this appears to point to the 32-bit version, the 64-bit version  
opens in the R buffer when I hit enter.

--Dale

On Jan 31, 2011 12:25pm, Martin Maechler <maechler <at> stat.math.ethz.ch> wrote:
> >>>>> Ruth M Ripley ruth <at> stats.ox.ac.uk>

> >>>>> on Sat, 11 Dec 2010 22:42:09 +0000 (GMT Standard Time)

> >>>>> writes:

> > Dear Martin, Thanks for your reply. Sorry, I should have said I

> > was testing the latest version I could find of Vincent Goulet's

> > wonderful packaging : emacs-23.2-modified-8.exe, with 32 bit

> > Windows XP. I was hoping the recent (post R-2.12.0) release of
(Continue reading)

Permalink | Reply | 31 comments |
headers
Sunny Srivastava | 1 Feb 2011 07:42
Picon
Gravatar

Re: Running gdb under emacs 23.1 and attaching to an ess-based R process

Hello ESS-list:

I am a happy ESS user but I haven't used it to debug C/C++ code. Recently, I
am trying to improve the speed of computations by using compiled C++ code in
my R function(s). But I am stuck at Step 8 mentioned in the previous email
communications.

I tried to follow the instructions mentioned by Professor Bates and
Professor Maechler, but in Step 8) when I type "c", I don't get back to
running R. Instead, I see "Continuing". (see below)

(gdb) b UpdateMean
Breakpoint 5 at 0xb721b0e7: file updateMean.cpp, line 4.
(gdb) c
Continuing.

I understand, my question may be really stupid, but when I try C-c C-c,
nothing happens (says: Text is read only) and if I try C-c C-q, I get a
prompt about quiting R. I have tried googling but I am unable to find any
solution.

Thank you in advance for any help or pointers.

S.

On Mon, Jan 17, 2011 at 8:13 AM, Douglas Bates <bates <at> stat.wisc.edu> wrote:

> Thank you, Martin.  This comes at a good time for me as I am still
> trying to debug some of the increment calculations in lme4a's glmer.
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Sunny Srivastava | 1 Feb 2011 08:09
Picon
Gravatar

Re: Running gdb under emacs 23.1 and attaching to an ess-based R process

Sorry, I forgot to mention that I am also on Ubuntu and Emacs 23.1.

On Tue, Feb 1, 2011 at 1:42 AM, Sunny Srivastava <research.baba <at> gmail.com>wrote:

> Hello ESS-list:
>
> I am a happy ESS user but I haven't used it to debug C/C++ code. Recently,
> I am trying to improve the speed of computations by using compiled C++ code
> in my R function(s). But I am stuck at Step 8 mentioned in the previous
> email communications.
>
> I tried to follow the instructions mentioned by Professor Bates and
> Professor Maechler, but in Step 8) when I type "c", I don't get back to
> running R. Instead, I see "Continuing". (see below)
>
> (gdb) b UpdateMean
> Breakpoint 5 at 0xb721b0e7: file updateMean.cpp, line 4.
> (gdb) c
> Continuing.
>
> I understand, my question may be really stupid, but when I try C-c C-c,
> nothing happens (says: Text is read only) and if I try C-c C-q, I get a
> prompt about quiting R. I have tried googling but I am unable to find any
> solution.
>
> Thank you in advance for any help or pointers.
>
> S.
>
> On Mon, Jan 17, 2011 at 8:13 AM, Douglas Bates <bates <at> stat.wisc.edu>wrote:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Martin Maechler | 1 Feb 2011 11:34
Picon
Favicon
Gravatar

Re: Finding Rterm in R 2.12.0 on Windows

>>>>> Dale W Steele <Dale.W.Steele <at> gmail.com>
>>>>>     on Tue, 01 Feb 2011 00:26:00 +0000 writes:

    > I've installed the most recent version of ESS from
    > subversion. ESS now finds both the 32-bit and 64-bit installed
    > versions of R-patched on my 64-bit Windows 7 system.

Thanks a lot, Dale, for the quick feedback!

    > One interesting issue. If I open an empty file test.R and
    > navigate via the ESS menu, Ie. "Start Process:Other and select
    > the 64 bit version, then the following text appears in the
    > buffer:

    > "ESS [S(R): C:/Program Files/R/R-2.12.1patched/bin/i386/Rterm.exe] starting data directory?"

    > Although this appears to point to the 32-bit version, the 64-bit
    > version opens in the R buffer when I hit enter.

Yes. That is actually another glitch, not at all related to
Windows or even R: Inside "[..]" the S or R version displayed is
sometimes wrong, i.e. the "previous" version instead of the one
that will be taken. 

One thing which *is* Windows-specific is that internally there
are two kind of version names, one being the short 
'R-2.12.1patched-64bit' one, which you also can use via
      M-x R-2.12.1patched-64bit
and the other the full path name (which will be shortened to the
8.3-short path name internally when the *call* to R is made).
(Continue reading)

Permalink | Reply | 30 comments |
headers
Douglas Bates | 1 Feb 2011 14:28
Picon
Favicon

Fwd: Running gdb under emacs 23.1 and attaching to an ess-based R process

I forgot to cc: the list on this reply.

---------- Forwarded message ----------
From: Douglas Bates <bates <at> stat.wisc.edu>
Date: Tue, Feb 1, 2011 at 7:27 AM
Subject: Re: [ESS] Running gdb under emacs 23.1 and attaching to an
ess-based R process
To: Sunny Srivastava <research.baba <at> gmail.com>

On Tue, Feb 1, 2011 at 12:42 AM, Sunny Srivastava
<research.baba <at> gmail.com> wrote:
> Hello ESS-list:
> I am a happy ESS user but I haven't used it to debug C/C++ code. Recently, I
> am trying to improve the speed of computations by using compiled C++ code in
> my R function(s). But I am stuck at Step 8 mentioned in the previous email
> communications.
> I tried to follow the instructions mentioned by Professor Bates and
> Professor Maechler, but in Step 8) when I type "c", I don't get back to
> running R. Instead, I see "Continuing". (see below)
> (gdb) b UpdateMean
> Breakpoint 5 at 0xb721b0e7: file updateMean.cpp, line 4.
> (gdb) c
> Continuing.

For me, the fact that nothing is shown after the "Continuing line" is
because the prompt has already been printed.  Simply hitting <Enter>
at that point produces a prompt (because you have given R an empty
line to parse and evaluate).

> I understand, my question may be really stupid, but when I try C-c C-c,
(Continue reading)

Permalink | Reply | 0 comments |
headers
Paul Johnson | 3 Feb 2011 07:43
Picon

Re: Finding Rterm in R 2.12.0 on Windows

On Tue, Feb 1, 2011 at 4:34 AM, Martin Maechler
<maechler <at> stat.math.ethz.ch> wrote:
>>>>>> Dale W Steele <Dale.W.Steele <at> gmail.com>
>>>>>>     on Tue, 01 Feb 2011 00:26:00 +0000 writes:

>    > One interesting issue. If I open an empty file test.R and
>    > navigate via the ESS menu, Ie. "Start Process:Other and select
>    > the 64 bit version, then the following text appears in the
>    > buffer:
>
>    > "ESS [S(R): C:/Program Files/R/R-2.12.1patched/bin/i386/Rterm.exe] starting data directory?"
>
>    > Although this appears to point to the 32-bit version, the 64-bit
>    > version opens in the R buffer when I hit enter.
>
> Yes. That is actually another glitch, not at all related to
> Windows or even R: Inside "[..]" the S or R version displayed is
> sometimes wrong, i.e. the "previous" version instead of the one
> that will be taken.

I've been watching this thread with interest.  Lately I've installed
Emacs and R on about 15 student computers with various versions of
windows. I've run into all of the various problems described in this
thread.  Emacs/ESS can't find R, etc. There are many ways to break
this chain of tools, some of which we could simplify for the ordinary
average non-computer science grad student.

Here are suggestions I am thinking of making to the R for Windows
packagers. Please tell me what you think:
(Continue reading)

Permalink | Reply | 29 comments |
headers
Stephen Eglen | 3 Feb 2011 11:26
Picon
Picon
Favicon

Re: Finding Rterm in R 2.12.0 on Windows

> 
> 2. The update.packages function should default to checkBuilt=T, so
> users who update R will, unless they actively resist, get the packages
> that match their installation.
> 
> The current install path, including the version number, creates a very
> confusing scenario for updates of packages.  Did you ever study the R
> for Windows FAQ discussion on what a user is supposed to do about the
> old lib dir and packages? I'm pretty good at computing and I can
> barely figure it out.  By adding checkBuilt=T, we completely eliminate
> that problem.
> 
> These suggestions bring the Windows install closer to the default
> Unix/Linux install. Install R in one place, don't keep version numbers
> in the install path, etc.

Paul makes some excellent points here.   I don't use Windows, but I too
am surprised about these complications.  Does anyone have experience of
other interfaces to R and how they deal with this?

As an aside, I've recently started using "homebrew" for my mac for
installing software, and I think it is pretty smart.  (Ok, this is a
unix machine, rather than windows, but same principle applies.)  It does
the install into say /usr/local/Cellar/R-2.12.1/...  and then puts
symlinks into /usr/local/bin so that the /usr/local/bin always points to
the most recently installed version.  Mac users - take a look:

http://mxcl.github.com/homebrew/

Stephen
(Continue reading)

Permalink | Reply | 2 comments |
headers
Martin Maechler | 3 Feb 2011 12:15
Picon
Favicon
Gravatar

ESS 5.13 released


Dear ESS users,

I have released ESS 5.13 a few moments ago.

The main reason and improvement is automatic support of "finding
R" for Windows and R versions 2.12.0 and newer.
Additionnally, there are other improvements in Roxygen and help
previewing, see also the
"New Features" below.
 ------------

In behalf of the ESS core team,

Martin Maechler, 
ETH Zurich

The following is part of the ANNOUNCE file that comes with ESS:
------------------------------------------------------------------

The ESS Developers proudly announce the release of ESS

   5.13

   Emacs Speaks Statistics (ESS) provides an intelligent, consistent
interface between the user and the software.  ESS interfaces with
R/S-PLUS, SAS, BUGS/JAGS, Stata and other statistical analysis packages
under the UNIX, GNU Linux, Microsoft Windows, Mac OS X and other
operating systems.  ESS is a package for the GNU Emacs and XEmacs text
editors whose features ESS uses to streamline the creation and use of
(Continue reading)

Permalink | Reply | 1 comment |
headers
Vincent Goulet | 3 Feb 2011 16:25
Picon
Favicon

Re: ESS 5.13 released

For users of my distribution of Emacs: I'll be somewhat late to the party here. Not that I can not build the
distribution, but I currently have no means to *distribute* it. 

Indeed, I realized yesterday that my web (and svn, and...) server apparently got stolen from my (former)
office at the university. Shame on me, you'll say, I hadn't planned this sort of need for a good backup.

I'll see what I can do in the next few days and will keep this group posted.

Best regards,

Vincent Goulet
Directeur général adjoint de la formation continue
Université Laval

Le 2011-02-03 à 06:15, Martin Maechler a écrit :

> 
> Dear ESS users,
> 
> I have released ESS 5.13 a few moments ago.
> 
> The main reason and improvement is automatic support of "finding
> R" for Windows and R versions 2.12.0 and newer.
> Additionnally, there are other improvements in Roxygen and help
> previewing, see also the
> "New Features" below.
> ------------
> 
> In behalf of the ESS core team,
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Rodney Sparapani | 3 Feb 2011 18:52
Picon
Gravatar

Re: Finding Rterm in R 2.12.0 on Windows

On 02/ 3/11 04:26 AM, Stephen Eglen wrote:
> Paul makes some excellent points here.   I don't use Windows, but I too
> am surprised about these complications.  Does anyone have experience of
> other interfaces to R and how they deal with this?
>
> As an aside, I've recently started using "homebrew" for my mac for
> installing software, and I think it is pretty smart.  (Ok, this is a
> unix machine, rather than windows, but same principle applies.)  It does
> the install into say /usr/local/Cellar/R-2.12.1/...  and then puts
> symlinks into /usr/local/bin so that the /usr/local/bin always points to
> the most recently installed version.  Mac users - take a look:
>
> http://mxcl.github.com/homebrew/
>
> Stephen

Well, in almost all matters R, I would defer to Stephen.  However, I
don't understand your remark.  On Mac OS X, whichever version of R you 
installed last (presumably the latest), is always found at /usr/bin/R
I must be missing your point entirely.

Rodney

______________________________________________
ESS-help <at> r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/ess-help
Permalink | Reply | 1 comment |

Gmane