[ESS] Debug mode puts point in the wrong buffer
Andreas Leha
andreas.leha at med.uni-goettingen.de
Thu Jun 20 10:41:49 CEST 2013
Hi Vitalie,
Vitalie Spinu <spinuvit at gmail.com> writes:
> >> Marius Hofert <marius.hofert at math.ethz.ch>
> >> on Wed, 19 Jun 2013 23:55:10 +0200 wrote:
>
> [...]
>
>
> > 1) ... M-C and means M-S-c (although this can never be clear since the
> > keys on a keybard are already shown as uppercase letters whereas they
> > are lowercase if not pressed with shift... but okay). Why not write
> > M-S-c? at least it's then clear that M-C does *not* mean 'meta +
> > control'.
>
> > 2) ... C-M-S-c for 'cont-multi' ... here, the 'Shift' is denoted by
> > 'S', probably to avoid the confusion with C-M-C, where the first 'C'
> > is 'Control' and the second 'C'.
>
> The keys are generated automatically. This is how emacs writes them. By
> convention C always precedes M, so M-C cannot mean Alt+Control, which
> are meaningless anyways.
>
> > Okay, I now got it to work, but only because I put the point back in
> > the *R* buffer... that's exactly the behavior I don't understand. Why
> > do I always have to switch in the other buffer (back go *R*) first
> > before I can enter debug commands (be it either RET or M-N [indeed,
> > RET is even simpler in this case :-)]).
>
> It should work from the R script buffer. Unless that script buffer is
> not associated with the process. It looks like a bug to me.
>
> Can you try the following. Create a new test.R and put the following
> into it:
>
>
> foo <- function(){
> browser()
> 1 + 2
> }
>
>
> foo()
>
> Evaluate the function with C-c C-c. Then foo(). Do you see visual
> debugger jumping and highlighting the line 1+2?
>
Sorry for hijacking this thread. But I just tried that and I do not
get the visual debugger. Do I need to enable that somehow?
Regards,
Andreas
PS: I am on ess-version : 13.05-1 [<unknown>]
More information about the ESS-help
mailing list