[ESS] How to make `ess-quit' *not* start up R if it is not already running?

[Vitalie Spinu]

Yes. I see the behavior that you have described. But what is your
realistic scenario? Are you calling ess-quit programatically?

 >>> Grant Rettke on Tue, 4 Nov 2014 18:47:11 -0600 wrote:

 > • Start up Emacs
 > • Confirm that all buffers that are file-based are closed but for the
 >   one that I am taking notes in
 >   • Messages and friends are still open
 >   • There is no R buffers open at this point with inferior processes
 >     attached
 > • Execute the key-press `M-x'
 > • Enter `ess-quit', choose `R', hit enter
 > • `R' process starts up, and inferior `R' process loads
 > • Buffer is open with a `R' REPL

 > What I am wondering, is in cases like this, where there is no `R' to
 > /quit/ in the first place, may I configure `ESS' to not do step 5,
 > because it looks like it is getting started up unnecessarily.

 > Of course, I am asking because I also wonder if it is just my machine
 > doing this :).

 > On Tue, Nov 4, 2014 at 1:10 PM, Vitalie Spinu <spinuvit at gmail.com> wrote:
 >> >>> Grant Rettke on Tue, 4 Nov 2014 12:23:37 -0600 wrote:
 >> 
 >> > Good afternoon, Sometimes I get lazy and run `ess-quit' to shut down
 >> > R buffers because I usually have a few open.
 >> 
 >> > Sometimes I get lazier and forget if I even have any R buffers
 >> > open. When I don't, ess starts up R for me, and then closes it at my
 >> > requests.
 >> 
 >> I don't understand this. Could you provide reproducible steps?
 >> 
 >> ESS will auto-start a process if you do an evaluation command or request
 >> help etc, and never auto-starts a new process out of the blue. If you
 >> have several processes running then you will be asked to choose from the
 >> list.
 >> 
 >> Vitalie