From: Daira Hopwood Date: Mon, 11 May 2015 14:05:42 +0000 (+0100) Subject: docs/frontends/CLI.rst: clarification. X-Git-Tag: allmydata-tahoe-1.10.1a1~15 X-Git-Url: https://git.rkrishnan.org/%5B/frontends/flags/index.php?a=commitdiff_plain;h=aa65426ad389a4d3ee40bc09d717db625be10e9a;p=tahoe-lafs%2Ftahoe-lafs.git docs/frontends/CLI.rst: clarification. The implementation (in [source:src/allmydata/scripts/common.py]) actually tests whether there is a slash anywhere before the first colon. Signed-off-by: Daira Hopwood --- diff --git a/docs/frontends/CLI.rst b/docs/frontends/CLI.rst index 6ec4ad3a..3a93cc86 100644 --- a/docs/frontends/CLI.rst +++ b/docs/frontends/CLI.rst @@ -204,7 +204,7 @@ The Tahoe-LAFS CLI commands use the same path syntax as ``scp`` and filename. Some commands (like "``tahoe cp``") use the lack of an alias to mean that you want to refer to a local file, instead of something from the Tahoe-LAFS filesystem. Another way to indicate this is to start the -pathname with a dot, slash, or tilde. +pathname with "./", "~/", "~username/", or "/". When you're dealing a single starting directory, the ``tahoe:`` alias is all you need. But when you want to refer to something that isn't yet