Hi Martin,
Thanks for your additional comments.
Perhaps my use case is in the minority, but after almost 20 years of using R,
primarily with Emacs/ESS on Windows, Linux and macOS over that time frame, I
never found the prior default behavior to be an issue for me. Thus, I had no
motivation to
I've also had 'nowait as my personal default for many years.I
find it also more appropriate when showing ESS to others, e.g. when
teaching etc.
Very importantly in practice: Keep in mind that prefixing i.e. C-u
<...> switches to visible (momentarily) which is also handy when
demo-ing,
Hi Alex,
Thanks for the clarification. Given that information, I found the related issue
report on Github:
https://github.com/emacs-ess/ESS/issues/998
reviewed the discussion there and ultimately, found the related commit.
I have modified the value to 'nowait for now, which seems to be a
The default value of ess-eval-visibly recently changed. You probably want
to customize it to t or nowait.
Alex
On Tue, May 19, 2020, 5:08 PM Marc Schwartz via ESS-help <
ess-help@r-project.org> wrote:
> Hi,
>
> A clarification, that when I do run the command, on a *single* line in the
> R
Hi,
A clarification, that when I do run the command, on a *single* line in the R
buffer, I am getting '>' characters for each line of R code in the region
passed, and I get '+' characters if there is a multiline region of code passed.
Thus, I might see the following single lines of output in
Hi All,
I just updated my ESS/Polymode installation today via melpa, and unless I am
missing something, I noticed that the use of ess-eval-region via "C-c C-r" does
not seem to echo the highlighted R code region into the R buffer, which it had
been doing until now.
The code does execute,
