This is a wishlist coupled with #393609. Please add an option to disable the *Debugger Console* and redirect all of its functionality to plain *R Console*. Perhaps with optional sidebar with "Next", "Step out", "Continue" and "Cancel" buttons which shows up when the RKWard detects a debugger context (and whose should be complete according to `browser()` implementation - see `?browser`). I would like to know the historical reason behind the decoupling of R Console and Debugger Console, especially when there is also a Debugger Frames window.
Thanks for all your suggestions. To answer the question for the "historical reason" why the Debugger Console is a separate window: The reason is that the R Console is not a "real" console, it's only designed to look that way. For instance if you are in the middle of writing a multi-line expression (e.g. a function definition), the R main loop is actually idle, instead of blocked waiting for the remainder of the statement. This has the important advantage that other commands (e.g. form a plugin, or a help search, or...) can be evaluated normally, without being blocked by the incomplete statement in the console. Now when debugging, R is blocked waiting for user input, which is a pretty different situation, and handled in a different window. Thus, technically, the two windows have not been decoupled, they simply have not been merged. You are probably right however, that this situation, too, could/should be handled inside the console window, somehow and/or in a window that looks much more like the console window.
Thanks for the info. I just want to thank you for your work on RKWard. I really love it, way more then RStudio and I tend to get itchy when people act like there is no alternative leading to absurd notions like the misconception that RStudio *is* R. However there were couple of usecases I noticed from coworkers where rkward is slightly lacking behind rstudio and those are mainly those I tried to address in my bugreports/suggestions. I don't know how much time/will you have regarding those, but if I can so something to help (apart of the actual coding where I don't have the necessary experience), just tell me.
Thanks for the nice feedback! If you want to help out, I suggest subscribing to rkward-devel@kde.org as a first step. Unfortunately, C++-coding is the most important bottleneck in our project, indeed, but when we need help with something else, we regularly post that on the mailing list, too. Packaging for your favourite distribution is one of the permanent tasks for instance.
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Valid wishlist item.
*** Bug 393609 has been marked as a duplicate of this bug. ***