From 43777708af20f53abbe268cc908854071d971d36 Mon Sep 17 00:00:00 2001 From: Robin Haberkorn Date: Mon, 8 Dec 2014 20:42:25 +0100 Subject: do not show possible completions for hidden files and directories * added platform-dependant file_is_visible() function --- doc/sciteco.7.template | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) (limited to 'doc/sciteco.7.template') diff --git a/doc/sciteco.7.template b/doc/sciteco.7.template index ef994e8..bad98cc 100644 --- a/doc/sciteco.7.template +++ b/doc/sciteco.7.template @@ -357,7 +357,9 @@ If \*(ST is not busy, is self-inserting and might be used as a regular command. T} .TE -.LP +. +.SS Auto Completion +. 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 @@ -365,6 +367,15 @@ 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. +.LP +When completing file names, hidden files are not considered for +completion unless a prefix of the hidden file's name has already +been typed. +On Unix, \*(ST considers files and directories beginning with \(lq.\(rq +as hidden. +On Windows, the \fIhidden\fP file attribute is evaluated. +On other platforms, \*(ST might not identify hidden files correctly. +.LP 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 -- cgit v1.2.3