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 compromise of sorts, given the issues raised. Thanks, Marc > On May 19, 2020, at 6:05 PM, Alex Branham <alex.bran...@gmail.com> wrote: > > 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 > 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 the R buffer, as > examples: > > >>>> > > or > > >>>>+>> > > after the command is run on a region of R code. > > Regards, > > Marc > > > > On May 19, 2020, at 4:51 PM, Marc Schwartz <marc_schwa...@me.com> wrote: > > > > 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, confirmed when I check for the resultant object. > > > > Am I missing new behavior, or perhaps a setting that changed someplace, or > > that I introduced a conflict with the updates today? > > > > Thanks, > > > > Marc Schwartz > > > > ______________________________________________ > ESS-help@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/ess-help ______________________________________________ ESS-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/ess-help
