[rkward-tracker] [ rkward-Bugs-1702734 ] Path completion confusion

SourceForge.net noreply at sourceforge.net
Wed Apr 18 08:29:10 UTC 2007

Bugs item #1702734, was opened at 2007-04-18 01:29
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: user interface
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Johannes Graumann (j_graumann)
Assigned to: Nobody/Anonymous (nobody)
Summary: Path completion confusion

Initial Comment:
This is 0.4.7-2 from the *.deb distributed here on Debian unstable.
I'm very pleased that path completion is now available in the R shell, but I find it a bit confusing. Please consider the following example:

Directory root

Now fire up rkward at the directory root. When calling 'setwd()' path completion will help you to navigate to "Dir1/Dir2". 'getwd()' now results in 'root/Dir1/Dir2', as expected. Now I want to 'source()' 'Script.R' and this is where the trouble starts. While the R console in rkward requires 'source("../Script.R")' to do what I want, path completion doesn't play along: it only offers options startin in the directory root where I started rkward. In my opinion, this is a bug and path completion should consider R's wd as its starting point.

Additionally consider the case of two script files script1.R and script2.R. Path completion will upon entering "scr" offer you the two options, but I would appreciate it, if it could also extend the possible path to the maximum of identical characters: "script" in this case - makes working with it much faster.


You can respond by visiting: 

More information about the rkward-tracker mailing list