to note it
failed.
Ross
From: Sparapani, Rodney <rspar...@mcw.edu>
Sent: Thursday, March 8, 2018 11:21:57 AM
To: Boylan, Ross
Cc: ess-help
Subject: Re: [ESS] Developing R packages under ESS
Hi Ross:
Oh, you mean Sweaving and knitting? That doe
Can anyone suggest to me a good way to develop R packages with ESS? "good"
here means that I can debug the code and make changes to the code without
rebuilding the whole package.
So far I've tried a bunch of different approaches, but none has quite worked.
1. When I had an old (or even new)
Thank you, Lionel and Rodney. That did the trick: the whole thing built,
including the documents.
Will everything actually work properly without xref? I assume xref was
required because something uses it.
I even got a build in the original directory after doing a make clean.
There are still
I did a make clean and then make, and now everything seems to be working.
If anyone has a more precise understanding of the source of the previous error,
I'd love to know. My theory was that the old elc files were screwing things up.
There were also a bunch of warnings associated with the
I just updated ESS to the latest git version
(62994e21c816e2bdd0e5b74f8cfdc00e6bb6c088), and now get the error about
ess-message being undefined on startup. Any ideas what the problem is?
The function ess-message seems to be defined in both ess-comp and ess-utils, so
perhaps this is some kind
I don't seem able to get my code to execute in SAS. Specifically, only the
first line in the region seems to be transmitted. Could the fact it is in a
file that does not have a .sas extension be a factor? Also, I have problems
exiting. BTW, http://ess.r-project.org/Manual/news.html doesn't
