From 2ae78885e8a5e7039972fef39cdd13a210cb5806 Mon Sep 17 00:00:00 2001 From: Robin Haberkorn Date: Thu, 7 Mar 2013 16:59:25 +0100 Subject: elaborate on auto-completions in sciteco(7) --- doc/sciteco.7.template | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/doc/sciteco.7.template b/doc/sciteco.7.template index 88b620a..c5055b1 100644 --- a/doc/sciteco.7.template +++ b/doc/sciteco.7.template @@ -354,6 +354,20 @@ If \*(ST is not busy, is self-inserting and might be used as a regular command. T} .TE +.LP +The immediate editing commands that perform auto-completions, do +so in a manner similar to Posix shells. +Upon first invocation they try to fully or partially complete the file +name (or token). +If no completion can be performed, the invocation will display a +list of file names (or tokens) beginning with the token to complete +in \*(ST's popup area. +Note that no additional expansions are performed before attempting +a completion, so for instance \(lq~/foo\(rq will not complete a file +in the user's home directory (tilde is not part of the file name but +tilde-expansions are performed by the shell). +\*(ST does however perform completions after string building so that +\(lq^EQ{$HOME}/foo\(rq could be completed. . . .SH ARITHMETICS AND EXPRESSIONS -- cgit v1.2.3