process control for different projects about ess HOT 4 CLOSED

Looking at the commit log, I reverted part of 88d611c,

diff --git a/lisp/ess-inf.el b/lisp/ess-inf.el
index 9ca3f455..aaff314c 100644
--- a/lisp/ess-inf.el
+++ b/lisp/ess-inf.el
@@ -828,6 +828,8 @@ to `ess-completing-read'."
                                                    'ess-dialect
                                                    (process-buffer (get-process (car lproc)))))
                                            (not (equal ess-local-process-name (car lproc)))
+                                           (equal (buffer-name (process-buffer (get-process (car lproc))))
+                                                  (funcall ess-gen-proc-buffer-name-function (car lproc)))
                                            (car lproc)))
                                     ess-process-name-list)
                             ;; append local only if running

By commenting out the two added lines, I've restored the ability to source lines/regions from different packages into the same R process, and I can see all processes when I try to ess-switch-process. I don't know if its behavior was intentional.

from ess.

Yes, I'm also suffering very badly from this. Even worse, for one "project" (I don't work with projects but in the same emacs with different *.R scripts and notably as R-core member with several different R versions, notably "R-devel" vs. released version of R, versus "yesterday's version" of R ...

It has become almost impossible to evaluate the same region of R code into two different *R* buffers,
may daily business as R Core developer, but also common when fixing a bug in other R code, running old version in one R buffer and the modified version in an (or several) other R session buffers.

A really simple hopefully reproducible (so many different versions of emacs nowadays, different setup..) example,
Can you reproduce:
Start Emacs, then M-x R .. (only one R process for now),
only now open a *.R file Try to eval some code. Instead of just "sending" it to the *R* buffer we had created (with M-x R) before, it asks me about where I would want the next R process to run ... argh...
and if I type C-c C-s (ess-switch-process), I do not even get the only existing running R as one of the choices!

from ess.

... and yes, @r2evans proposal solve the big problem for me.
As this is "uniformly better" than previous, and a reversion to previously blameless behavior (I do not work with ess-remote, though) I did commit & push this for now (and failed to send this comment before I did ...)

from ess.

Looks like this is from your patch @ihor-radchenko, could you take a look please?

from ess.