unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Hosley <kbrownk@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Can't open R in Emacs
Date: Sat, 04 Aug 2007 16:54:22 -0700	[thread overview]
Message-ID: <1186271662.441195.209340@g4g2000hsf.googlegroups.com> (raw)
In-Reply-To: <1186263225.628427.122000@e9g2000prf.googlegroups.com>

On Aug 4, 5:33 pm, the matt <m...@kettlewell.net> wrote:
> On Aug 4, 3:15 pm, Hosley <kbro...@gmail.com> wrote:
>
>
>
> > On Aug 4, 10:43 am, Marc Schwartz <marc_schwa...@comcast.net> wrote:
>
> > > Peter Dyballa <Peter_Dyba...@Web.DE> writes:
> > > > Am 04.08.2007 um 00:30 schrieb Hosley:
>
> > > >> I can open R by clicking on my desktop "R 2.5.0" icon, or by opening
> > > >> from "C:\Program Files\R\R-2.5.0\bin\Rgui.exe"
>
> > > > You certainly won't be running R's GUI in GNU Emacs, you'll need to
> > > > find the "simple" command line oriented utility, R.exe or such. The
> > > > Swedish URL you provided mentions C:\tools\bin\ to contain R.
>
> > > No.  The 'tools' directory is for other purposes, such as compiling R from source
> > > and/or creating add-on packages.
>
> > > In this case, the terminal based executable on Windows, as per the link I
> > > provided is called 'Rterm.exe'.
>
> > > Note also that the full path to the application, which on Windows has a space
> > > in it, needs to use the '~1' contraction. So for R 2.5.1 it should be something
> > > like:
>
> > >   (setq inferior-R-program-name "C:/progra~1/R/R-2.5.1/bin/Rterm.exe")
>
> > > if you are going to use that approach in .emacs. Again, that is described in the
> > > aforementioned ESS manual.
>
> > > HTH,
>
> > > Marc
>
> > I want to alter the default in emacs, so I guess I want to create/
> > modify an initialization file (.emacs) with the command you've
> > provided above. I read the ESS manual and other stuff online, but I'm
> > still clueless! Where am I supposed to find or put this .emacs file?
> > Do I just create one in C:\devel\emacs\lisp by creating a text file,
> > typing in (setq inferior-R-program-name "C:/progra~1/R/R-2.5.1/bin/
> > Rterm.exe"), saving, then changing the format to .emacs? I know
> > literally nothing about command line programming, and much of this
> > manual is beyond my understanding.
>
> > Thanks again,
> > Hos
>
> I really have to wonder if running R inside of Emacs is a good idea
> for you.  It seems that you would be better off running R as a
> standalone.
>
> I don't know much about Windows init files, but I suspect  that a
> quick internet search for "Windows Emacs startup files" would give
> enough information to me so that I would'nt have to ask a newsgroup to
> do my homework for me.  There is also the GNU emacs manual that is
> pretty good at identifying the locations of all the startup scripts.
>
> .emacs files are customized in Emacs-Lisp (a LISP dialect), and I
> suspect that once you do figure out how to find this file, you will be
> further overwhelmed with getting it customized.
>
> I suggest that you stick with learning R (it is rather extensive in
> its own right)
>
> As to answer your question, if it (.emacs) isn't created, you will
> need to create it and put into the directory of your "HOME" env
> variable. If you don't have one defined, it will look in C:\
>
> Just my thoughts.
>
> Matt

I appreciate your advice. Unfortunately I have to follow the
instructions provided for the crash course (5 days 8 hours a day) I'm
required to take in R. I initially tried reading the manuals, but I
was getting overwhelmed with all of the scenarios that did not relate
to my issue. I was hoping there was an easy answer I was missing, and
I didn't mean for it to get to a point where others were doing my
homework for me (though I greatly appreciate all of the help and have
learned a lot in from what people have suggested). I'll read through
the manual again tomorrow, and if I find an answer, I'll post my own
step by step directions just in case it might help others.

Hos

  reply	other threads:[~2007-08-04 23:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-03 17:51 Can't open R in Emacs Hosley
2007-08-03 20:48 ` Peter Dyballa
2007-08-03 21:32   ` Eli Zaretskii
     [not found] ` <mailman.4358.1186174145.32220.help-gnu-emacs@gnu.org>
2007-08-03 21:32   ` Hosley
2007-08-03 23:04     ` Peter Dyballa
2007-08-03 21:32 ` Eli Zaretskii
     [not found] ` <mailman.4365.1186176834.32220.help-gnu-emacs@gnu.org>
2007-08-03 22:30   ` Hosley
2007-08-04  8:18     ` Peter Dyballa
2007-08-04 11:28       ` Reiner Steib
2007-08-04  8:25     ` Eli Zaretskii
     [not found]     ` <mailman.4375.1186215516.32220.help-gnu-emacs@gnu.org>
2007-08-04 14:43       ` Marc Schwartz
2007-08-04 21:15         ` Hosley
2007-08-04 21:33           ` the matt
2007-08-04 23:54             ` Hosley [this message]
2007-08-05  3:56             ` Hosley
2007-08-04 23:08           ` Peter Dyballa
2007-08-05  3:08           ` Eli Zaretskii
2007-08-04  2:56 ` Dieter Wilhelm
2007-08-04  3:14 ` Marc Schwartz
2007-08-04  4:58   ` Hosley
2007-08-21  6:33     ` poti

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1186271662.441195.209340@g4g2000hsf.googlegroups.com \
    --to=kbrownk@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).