1RKWARD(1) KDE User's Manual RKWARD(1)
2
6 rkward - A KDE frontend to R
7
9 rkward [--evaluate Rcode] [--debug-level level] [--debug-flags flags]
10 [--debug-output where] [--backend-debugger debugger_command]
11 [--r-executable path_to_executable] [--reuse]
12 [--nowarn-external] [KDE Generic Options] [Qt Generic Options]
13 [files_to_open]
14
16 RKWard is the a KDE-based GUI and IDE for the R scripting language for
17 statistical computing.
18 For more information, please refer to the RKWard website[1], and the
20 documentation provided inside RKWard.
21
23 --evaluate Rcode
24 The given R code is evaluated after RKWard has started, and after
25 any specified workspace is loaded. Mostly useful for automated
26 testing.
27 --debug-level level
29 Verbosity of debug output. 0-5, where 0 is no output, 5 is all
30 output including function trace information. Default is 2.
31 --debug-output where
33 Where to send debug output. Default is to store it in a file in the
34 temporary directory. Specifying "terminal" will write debug output
35 to stderr, instead (useful for debugging startup problems). Note
36 that debug output from the backend process is always stored in a
37 file.
38 --debug-flags flags
40 Configure which sections of code to debug. Flags are given as a
41 binary number. Refer to the source files for documentation, as this
42 really is an internal option.
43 --backend-debugger command
45 Run the RKWard backend through the specified debugger command. To
46 add command line options to the debugger command, enclose them in
47 single quotes ('') together with the command. NOTE: Debugger
48 arguments will be split by spaces. If this is not appropriate, you
49 will have to write your own wrapper script for invoking the
50 debugger. Also, make sure to redirect all debugger output and/or
51 input as appropriate. See the examples.
52 --r-executable command
54 In the case of several R installations, specify the installation to
55 use, e.g. /usr/bin/R. Note that the rkward R library must have been
56 installed to this installation of R, or startup will fail.
57 --reuse
59 If an instance of RKWard is already running, bring that to the
60 front, and open files_to_open. Note that all other command line
61 options will be ignored in case an instance is reused.
62 --nowarn-external
64 Usually, when invoking RKWard plugins from the command line (i.e.
65 when files_to_open contains urls of the form
66 rkward://runplugin/...), RKWard will show a warning that such urls
67 could be used to trigger malicious actions on your system. This
68 warning applies specifically to links found on untrusted websites,
69 or other untrusted external sources. If you want to script RKWard
70 locally, you can avoid this warning by adding --nowarn-external to
71 the command line.
72 files_to_open
74 You can specify any number of file names or urls for RKWard to
75 open. Usually this will be either workspace files, workplace files,
76 R script files, or rkward://-urls (e.g. for starting with a plugin
77 dialog). Specifying more than one workspace file will lead to the
78 workspaces being merged together, and is not recommended.
79
81 R(1)
82
84 # Start with the t-test dialog
85 rkward --nowarn-external rkward://runplugin/rkward::t_test/
86 # Open two script files in a running instance of RKWard (or in a fresh instance, if RKWard is not running)
87 rkward --reuse file_a.R file_b.R
88 # Run the rkward backend through valgrind
90 rkward --backend-debugger 'valgrind --log-file=valgrind.log'
91
93 RKWard was written by Thomas Friedrichsmeier and the RKWard team. See
94 the RKWard website[1].
95
97 Thomas Friedrichsmeier <rkward-devel@kde.org>
98 RKWard man page.
99
101 1. the RKWard website
102 http://rkward.kde.org/
103K Desktop Environment 2017-05-20 RKWARD(1)