Doug Kelkhoff

Now that we have the browser hook, we can much more easily capture browser steps (`n`, `c`), but we still need the task callback to emit environment update messages, so...

Great idea! Will definitely add a section specifically for parser options.

> Have you mentioned these issues in the R-devel mailing list? @sebffischer I haven't. I've never raised a feature proposal like that before, so I'm not exactly sure where to...

@jonlachmann thanks for the nudge. I've drafted a few requests to the R mailing list and/or the r-contributors slack, but ultimately always felt like I must be missing something if...

Thanks @sebffischer for drawing my attention to [HenrikBengtsson/Wishlist-for-R](https://github.com/HenrikBengtsson/Wishlist-for-R). I filed this as a proposal in https://github.com/HenrikBengtsson/Wishlist-for-R/issues/159

- [original r-project bugs discussion](https://bugs.r-project.org/show_bug.cgi?id=18590) - [@ltierney example on how to use browser hooks](https://github.com/ltierney/browserhook) - [r-source commits related to browser hooks](https://github.com/search?q=repo%3Awch%2Fr-source+BROWSER_HOOK&type=commits)

Note, this probably means the next stage of this project will only work on `R-devel`, compiled with the `-DUSE_BROWSER_HOOK` flag set. Because I build R from source ever few years...

Taking some notes on Luke's browser hooks implementation. More of a "user acceptance testing" style feedback, with my own thoughts on this as an API for hooking into the browser:...

> is it supposed to currently work [within neovim] in its current state? When I was working in this, neovim was what I used to test to see if it...

Ah, that's a good point. You're imagining a situation like: ```r 1| lapply( 2| list(1, 2, 3), 3| function(i) { o 4| print(i) 5| } 6| ) ``` Yeah... that's...