summaryrefslogtreecommitdiffstats
path: root/doc/zipfs.n
diff options
context:
space:
mode:
authorapnadkarni <apnmbx-wits@yahoo.com>2023-10-04 10:00:00 (GMT)
committerapnadkarni <apnmbx-wits@yahoo.com>2023-10-04 10:00:00 (GMT)
commit06ae8c6d9e8de0918c8fdaef03556e07aef9de1d (patch)
tree6640da7d8646d80ca4c4b463d0d537beb86cc10e /doc/zipfs.n
parent6a7c03014a876e280e451e8070af21e057fb55b6 (diff)
downloadtcl-06ae8c6d9e8de0918c8fdaef03556e07aef9de1d.zip
tcl-06ae8c6d9e8de0918c8fdaef03556e07aef9de1d.tar.gz
tcl-06ae8c6d9e8de0918c8fdaef03556e07aef9de1d.tar.bz2
Misc fixes in zipfs manpage
Diffstat (limited to 'doc/zipfs.n')
-rw-r--r--doc/zipfs.n6
1 files changed, 5 insertions, 1 deletions
diff --git a/doc/zipfs.n b/doc/zipfs.n
index 2a29a67..26b45a6 100644
--- a/doc/zipfs.n
+++ b/doc/zipfs.n
@@ -43,6 +43,10 @@ simple encryption, sufficient to prevent casual inspection of their contents
but not able to prevent access by even a moderately determined attacker.
Strong encryption, multi-part archives, platform metadata,
zip64 formats and other compression methods like bzip2 are not supported.
+.PP
+Files within mounted archives can be written to but new files or directories
+cannot be created. Further, modifications to files are limited to the
+mounted archive in memory and are not persisted to disk.
.TP
\fBzipfs canonical\fR ?\fImountpoint\fR? \fIfilename\fR ?\fIinZipfs\fR?
.
@@ -116,7 +120,7 @@ In the third form, the command mounts the ZIP archive \fIzipfile\fR as a Tcl vir
filesystem at \fImountpoint\fR. After this command executes, files contained
in \fIzipfile\fR will appear to Tcl to be regular files at the mount point.
If \fImountpoint\fR is
-specified as an empty string, it is defaulted to the file path.
+specified as an empty string, it is defaulted to the \fB[zipfs root]\fR.
.PP
\fBNB:\fR because the current working directory is a concept maintained by the
operating system, using \fBcd\fR into a mounted archive will only work in the