On 08/04/2014, 6:05 PM, Paul Murtaugh wrote:
It appears to be a difference between versions 2.* and 3.* in the way
that a newline ('enter') is handled at the browser prompt. Formerly, it
would continue execution of the function; now it kicks you into
debugging mode. To get the old behavior, you
It appears to be a difference between versions 2.* and 3.* in the way
that a newline ('enter') is handled at the browser prompt. Formerly, it
would continue execution of the function; now it kicks you into
debugging mode. To get the old behavior, you need to enter 'c' at the
browser prompt.
On 08/04/2014 3:34 PM, Paul Murtaugh wrote:
This is something peculiar about the environment on one particular linux
box, because it doesn't happen on other computers. Whenever I invoke
browser() inside a function, it automatically enters debugging mode,
with line-by-line execution of code:
>
This is something peculiar about the environment on one particular linux
box, because it doesn't happen on other computers. Whenever I invoke
browser() inside a function, it automatically enters debugging mode,
with line-by-line execution of code:
> dum <- function() { browser(); x <- rnorm(1
4 matches
Mail list logo
