Thanks for adding this option. I vastly prefer this behavior for reasons
having nothing to do with source references.

If I try to eval a paragraph of code and there is an error in the middle of
the paragraph, it should not blithely continue trying to eval code after
the error; I should not have to scroll back up the transcript to detect
whether an error nullified the effect of one of my statements.

The "steamroll ahead with no regard to anything" behavior that occurs
without ess-inject-source was, seriously, my biggest complaint about ESS.

Peter


On Thu, Jun 20, 2013 at 1:19 PM, Vitalie Spinu <spinuvit@gmail.com> wrote:

>
> [...]
>
>
>  > ... If I use 'C-c C-c' to evaluate the function, then the line is
>  > highlight. However, if I use C-RET to evaluate each everything 'step
>  > by step', then debug mode is on (red DB), but the line '1+2' is *not
>  > highlighted*. That's certainly a bug, right?
>
> No. The behavior does depend on the way you evaluate it. There is no
> feasible way to insert source references into the function if you
> evaluate it line by line. Only C-c C-c, C-c C-f,  C-c C-l and C-c C-b
> are inserting source by default. C-c C-c inserts only when function is
> detected.
>
> You can set ess-inject-source to t (see the docs in ESS dev). Then all
> the evaluation commands in ESS will inject the source references. But
> that comes with a price - you won't be able to accumulate the code as in
> your example with C-RET.
>
>     Vitalie
>
> ______________________________________________
> ESS-help@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/ess-help
>

	[[alternative HTML version deleted]]

