[Bug] Testing: ESS (*R*, R (newest)) starting data directory?

[Bug] Testing: ESS (*R*, R (newest)) starting data directory?

[Achim Gratz]

This is probably caused by an update of ESS rather than some change in
Org, however Org should probably bind ess-ask-for-ess-directory to nil
during batch testing at least.  There may be other customizations that
need to be taken care of, I also get

Cannot read history file […]/org-mode/testing/examples/.Rhistory

in the testing output.  Someone who actually uses ESS on a regular basis
needs to decide the appropriate course.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada

Re: [Bug] Testing: ESS (*R*, R (newest)) starting data directory?

[Charles C. Berry]

[-- Attachment #1: Type: text/plain, Size: 527 bytes --]

On Sun, 24 Jan 2016, Achim Gratz wrote:

>
> This is probably caused by an update of ESS rather than some change in
> Org,

Nope. I failed to let bind ess-ask-for-ess-directory in adding a test a 
few days ago.

Fixed in commit 27b590c39551f9aae79d801f61125cbaf1bd896c.

>
> Cannot read history file […]/org-mode/testing/examples/.Rhistory
>
> in the testing output.  Someone who actually uses ESS on a regular basis
> needs to decide the appropriate course.
>

Now fixed by binding `ess-history-file' to nil.

Thanks,

Chuck

Re: [Bug] Testing: ESS (*R*, R (newest)) starting data directory?

[Achim Gratz]

Charles C. Berry writes:
> Nope. I failed to let bind ess-ask-for-ess-directory in adding a test
> a few days ago.
>
> Fixed in commit 27b590c39551f9aae79d801f61125cbaf1bd896c.
[…]
> Now fixed by binding `ess-history-file' to nil.


Thank you.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds