[OS X Emacs] Directory for loading ESSR

[Braun, Michael]

Yes, I have.  Continuously, for many years.  Thank you for asking.

This is a new problem that I started noticing I *think* after upgrading to Mojave about a week ago (which I appear to have omitted from my original question), but I cannot be sure it doesn’t go back to an Aquamacs update earlier than that.  I did try retracing my steps, and this directory issue is where I ended up.  When I run the functions in .load.R directly, the help problem goes away.  So I do think the issue is that Aquamacs can no longer find the right ESS files.  But my Emacs Lisp skills are close to nil, hence the need for some help.

Thanks,

Michael



> >  On Dec 14, 2018, at 16:09 PM, Lefterov, Iliya <iliya.lefterov at gmail.com> wrote:
> 
> > Have you used ESS within Aquamacs before successfully…? Best! 
> 
>>  > On Dec 14, 2018, at 12:51 PM, Braun, Michael <braunm at mail.smu.edu> wrote: 
>> > 
>> > When launching an R process via ESS (M-x R), I get the following Emacs message: 
>> > 
>> > load ESSR: + + + Error in file(filename, "r", encoding = encoding) : 
>> > cannot open the connection 
>> > In addition: Warning message: 
>> > In file(filename, "r", encoding = encoding) : 
>> > cannot open file ’/Users/dr/Nightly/master/aquamacs-emacs.git/lisp/aquamacs/edit-modes/ess-mode/etc/ESSR/R/.load.R’: No such file or directory 
>> > 
>> > It appears somewhere in the Aquamacs build process, the directory path on the builder’s computer is not replaced, as my user name is not “dr”. Thus, Aquamacs cannot find ESSR. This is causing problems with using the help functions in R. For example: 
>> > 
>> >> ?mean 
>> > Error in .ess.help("mean") : could not find function ".ess.help" 
>> > 
>> > The problem occurs when I use either the stable 3.4 version of Aquamacs, or the latest nightly build. ESS version is 18.10.2, although I had the problem with 18.10 as well. Not sure if it matters, but the latest ESS is a Melpa version. 
>> > 
>> > Any suggestions or fixes would be appreciated. 
>> > 
>> > Thanks. 
>> > 
>> > Michael