RKWARD(1) | KDE User's Manual | RKWARD(1) |
NAME¶
rkward - A KDE frontend to RSYNOPSIS¶
rkward [--evaluate Rcode] [--debug-level level] [--debug-flags flags] [--debugger debugger_command [debugger_args [--]]] [--backend-debugger debugger_command] [--r-executable path_to_executable] [--reuse] [--nowarn-external] [KDE Generic Options] [Qt Generic Options] [files_to_open]
DESCRIPTION¶
RKWard is the a KDE-based GUI and IDE for the R scripting language for statistical computing.For more information, please refer to the RKWard website[1], and the documentation provided inside RKWard.
OPTIONS¶
--evaluate Rcode--debug-level level
--debug-flags flags
--debugger command [arguments [--]]
Note that there are a number of pitfalls that may complicate setting up the debugger session as desired. Consider starting RKWard with option \-\-debug-lebel 3, which will print the effective command line used to start the frontend (but not all relevant environment variables). As one hint, you will generally need to pass a separator argument with the debugger arguments, e.g. rkward --debugger gdb --args. Under Windows, the debugger command will not be connected to stdin. For interactive debugging, consider using a graphical debugger.
--backend-debugger command
--r-executable command
--reuse
--nowarn-external
files_to_open
SEE ALSO¶
R(1)EXAMPLES¶
# Start with the t-test dialog rkward --nowarn-external rkward://runplugin/rkward::t_test/ # Open two script files in a running instance of RKWard (or in a fresh instance, if RKWard is not running) rkward --reuse file_a.R file_b.R # Run the rkward backend through valgrind rkward --backend-debugger 'valgrind --log-file=valgrind.log'. # Debug the frontend through gdb rkward --debugger 'gdb --args'
AUTHORS¶
RKWard was written by Thomas Friedrichsmeier and the RKWard team. See the RKWard website[1].AUTHOR¶
Thomas Friedrichsmeier <rkward-devel@kde.org>NOTES¶
- 1.
- the RKWard website
2015-12-07 | K Desktop Environment |