R help - Nov 2016 - browser() pre 3.1 behaviour

Dear R help list,I have been using the "browser()" function for a long
time now to debug my function code. However, since 3.1 (I think) the behaviour
has changed that browser() (or the debug interface) is being called also when a
loop is being executed (copy pasted to the R interface). So I have to cancel
this browser or confirm each iteration of the loop. And this I believe also
extends to various other calls. In the end I would like to set up my R to behave
like it did in R <= 3.0. This has been so bothersome, that I was sticking
with old R versions, but now some packages are no longer supported in these old
versions.
How to set up browser() to follow the old behaviour??
I have been looking for some time now to find an answer to this on the internet,
but was so far unsuccessful, I would be grateful for any help.best,?Falk
Hildebrand
PS: I think this is the change that occured in 3.1:
[R] R 3.1.0 is released

  
|  
|   |  
[R] R 3.1.0 is released
   |  |

  |

 
 DEBUGGING:

   * The behaviour of the code browser has been made more consistent,
     in part following the suggestions in PR#14985.

   * Calls to browser() are now consistent with calls to the browser
     triggered by debug(), in that Enter will default to n rather than
     c.

   * A new browser command s has been added, to "step into" function
     calls.

   * A new browser command f has been added, to "finish" the current
     loop or function.

   * Within the browser, the command help will display a short list of
     available commands.
	[[alternative HTML version deleted]]

On 23/11/2016 6:51 AM, Falk Hildebrand via R-help wrote:
> Dear R help list,I have been using the "browser()" function for a
long time now to debug my function code. However, since 3.1 (I think) the
behaviour has changed that browser() (or the debug interface) is being called
also when a loop is being executed (copy pasted to the R interface).
This doesn't really parse for me.  Could you please post detailed 
instructions for what you're doing and describe what you're seeing?

Duncan Murdoch
>   So I have to cancel this browser or confirm each iteration of the loop.
And this I believe also extends to various other calls. In the end I would like
to set up my R to behave like it did in R <= 3.0. This has been so
bothersome, that I was sticking with old R versions, but now some packages are
no longer supported in these old versions.
> How to set up browser() to follow the old behaviour??
> I have been looking for some time now to find an answer to this on the
internet, but was so far unsuccessful, I would be grateful for any help.best,
Falk Hildebrand
> PS: I think this is the change that occured in 3.1:
> [R] R 3.1.0 is released
>
>    
> |
> |   |
> [R] R 3.1.0 is released
>     |  |
>
>    |
>
>   
>   DEBUGGING:
>
>     * The behaviour of the code browser has been made more consistent,
>       in part following the suggestions in PR#14985.
>
>     * Calls to browser() are now consistent with calls to the browser
>       triggered by debug(), in that Enter will default to n rather than
>       c.
>
>     * A new browser command s has been added, to "step into"
function
>       calls.
>
>     * A new browser command f has been added, to "finish" the
current
>       loop or function.
>
>     * Within the browser, the command help will display a short list of
>       available commands.
> 	[[alternative HTML version deleted]]
>
> ______________________________________________
> R-help at r-project.org mailing list -- To UNSUBSCRIBE and more, see
> https://stat.ethz.ch/mailman/listinfo/r-help
> PLEASE do read the posting guide
http://www.R-project.org/posting-guide.html
> and provide commented, minimal, self-contained, reproducible code.