https://bugs.kde.org/show_bug.cgi?id=393610
Thomas Friedrichsmeier <thomas.friedrichsme...@ruhr-uni-bochum.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |thomas.friedrichsmeier@ruhr
| |-uni-bochum.de
--- Comment #1 from Thomas Friedrichsmeier
<thomas.friedrichsme...@ruhr-uni-bochum.de> ---
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.
--
You are receiving this mail because:
You are watching all bug changes.
