Behavior of C-c C-n

[Paul Johnson]

I don't know if I understand your point.  In Windows or Linux with the 
newest ESS,  C-c C-n causes the current line to run and it advances the 
cursor location to the next line in the code.  I don't understand what 
you mean "would like my R process window to keep up with the current 
submitted code."

I see the R commands run in the ESS *R* window.

However, I do see the issue, which I *THINK* was always present in ESS, 
that the R session running under ESS does not add the commands to the R 
history that are sent over from the R code buffer. So Control-up-arrow 
does not cause the ESS *R* buffer to step backwards through the commands 
that ESS submitted.

Patrick Connolly wrote:
> On Mon, 17-May-2004 at 04:25PM -0400, Martin Henry H. Stevens wrote:
> 
> |> Mac OS X 10.3.3
> |> GNU Emacs 21.3.50.1
> |> ESS 5.2.0
> |> R 2.0.0
> |> 
> |> When I use C-c C-n to submit a line of R code from my source code
> |> to the R process (and step to the next line), I would like my R
> |> process window to keep up with the current submitted
> |> code. Currently, it does not, yet I know that in other
> |> implementations, this keeping-up by the R process has
> |> occurred. What is "normal" and how might I change this behavior?
> 
> It's the same with 
> 
> GNU Emacs 21.2.1
> ESS 5.2.0
> R 1.9.0
> platform i686-pc-linux-gnu
> 
> With previous versions of ESS, it did what you and I prefer.  I
> previously used 5.1.23 which did work "properly".  I tried the
> ess-5.2.0rc3, for a short time, and it wasn't a problem with it
> either.  If the change is intentional, I didn't notice its being
> mentioned (but I'm not all that observant).
> 
> I'd also be very interested in learning how to change it back.
> 


-- 
Paul E. Johnson                       email: pauljohn at ku.edu
Dept. of Political Science            http://lark.cc.ku.edu/~pauljohn
1541 Lilac Lane, Rm 504
University of Kansas                  Office: (785) 864-9086
Lawrence, Kansas 66044-3177           FAX: (785) 864-5700