NAME<\/a> ______________________________________________________________________________<\/p>\n file \u2212 Manipulate file names and attributes<\/p>\n file<\/b> option name<\/i> ?arg arg …<\/i>? ______________________________________________________________________________<\/p>\n This command provides several operations on a file\u2019s name or attributes. Name<\/i> is the name of a file; if it starts with a tilde, then tilde substitution is done before executing the command (see the manual entry for filename<\/b> for details). Option<\/i> indicates what to do with the file name. Any unique abbreviation for option<\/i> is acceptable. The valid options are: Returns a decimal string giving the time at which file name<\/i> was last accessed. If time<\/i> is specified, it is an access time to set for the file. The time is measured in the standard POSIX fashion as seconds from a fixed starting time (often January 1, 1970). If the file does not exist or its access time cannot be queried or set then an error is generated. On Windows, FAT file systems do not support access time.<\/p>\n file attributes<\/b> name<\/i> This subcommand returns or sets platform specific values associated with a file. The first form returns a list of the platform specific flags and their values. The second form returns the value for the specific option. The third form sets one or more of the values. The values are as follows:<\/p>\n On Unix, \u2212group<\/b> gets or sets the group name for the file. A group id can be given to the command, but it returns a group name. \u2212owner<\/b> gets or sets the user name of the owner of the file. The command returns the owner name, but the numerical id can be passed when setting the owner. \u2212permissions<\/b> sets or retrieves the octal code that chmod(1) uses. This command does also has limited support for setting using the symbolic attributes for chmod(1), of the form [ugo]?[[+\u2212=][rwxst],[…]], where multiple symbolic attributes can be separated by commas (example: u+s,go\u2212rw<\/b> add sticky bit for user, remove read and write permissions for group and other). A simplified ls<\/b> style string, of the form rwxrwxrwx (must be 9 characters), is also supported (example: rwxr\u2212xr\u2212t<\/b> is equivalent to 01755). On versions of Unix supporting file flags, \u2212readonly<\/b> gives the value or sets or clears the readonly attribute of the file, i.e. the user immutable flag uchg<\/b> to chflags(1).<\/p>\n On Windows, \u2212archive<\/b> gives the value or sets or clears the archive attribute of the file. \u2212hidden<\/b> gives the value or sets or clears the hidden attribute of the file. \u2212longname<\/b> will expand each path element to its long version. This attribute cannot be set. \u2212readonly<\/b> gives the value or sets or clears the readonly attribute of the file. \u2212shortname<\/b> gives a string where every path element is replaced with its short (8.3) version of the name. This attribute cannot be set. \u2212system<\/b> gives or sets or clears the value of the system attribute of the file.<\/p>\n On Mac OS X and Darwin, \u2212creator<\/b> gives or sets the Finder creator type of the file. \u2212hidden<\/b> gives or sets or clears the hidden attribute of the file. \u2212readonly<\/b> gives or sets or clears the readonly attribute of the file. \u2212rsrclength<\/b> gives the length of the resource fork of the file, this attribute can only be set to the value 0, which results in the resource fork being stripped off the file.<\/p>\n file channels<\/b> ?pattern<\/i>?<\/p>\n If pattern<\/i> is not specified, returns a list of names of all registered open channels in this interpreter. If pattern<\/i> is specified, only those names matching pattern<\/i> are returned. Matching is determined using the same rules as for string match<\/b>.<\/p>\n file copy<\/b> ?\u2212force<\/b>? ?\u2212\u2212<\/b>? source target<\/i> The first form makes a copy of the file or directory source<\/i> under the pathname target<\/i>. If target<\/i> is an existing directory, then the second form is used. The second form makes a copy inside targetDir<\/i> of each source<\/i> file listed. If a directory is specified as a source<\/i>, then the contents of the directory will be recursively copied into targetDir<\/i>. Existing files will not be overwritten unless the \u2212force<\/b> option is specified (when Tcl will also attempt to adjust permissions on the destination file or directory if that is necessary to allow the copy to proceed). When copying within a single filesystem, file copy<\/i> will copy soft links (i.e. the links themselves are copied, not the things they point to). Trying to overwrite a non-empty directory, overwrite a directory with a file, or overwrite a file with a directory will all result in errors even if \u2212force<\/b> was specified. Arguments are processed in the order specified, halting at the first error, if any. A \u2212\u2212<\/b> marks the end of switches; the argument following the \u2212\u2212<\/b> will be treated as a source<\/i> even if it starts with a \u2212<\/b>.<\/p>\n file delete<\/b> ?\u2212force<\/b>? ?\u2212\u2212<\/b>? ?pathname<\/i> … ?<\/p>\n Removes the file or directory specified by each pathname<\/i> argument. Non-empty directories will be removed only if the \u2212force<\/b> option is specified. When operating on symbolic links, the links themselves will be deleted, not the objects they point to. Trying to delete a non-existent file is not considered an error. Trying to delete a read-only file will cause the file to be deleted, even if the \u2212force<\/b> flags is not specified. If the \u2212force<\/b> option is specified on a directory, Tcl will attempt both to change permissions and move the current directory \u201cpwd\u201d out of the given path if that is necessary to allow the deletion to proceed. Arguments are processed in the order specified, halting at the first error, if any. A \u2212\u2212<\/b> marks the end of switches; the argument following the \u2212\u2212<\/b> will be treated as a pathname<\/i> even if it starts with a \u2212<\/b>.<\/p>\n file dirname<\/b> name<\/i><\/p>\n Returns a name comprised of all of the path components in name<\/i> excluding the last element. If name<\/i> is a relative file name and only contains one path element, then returns \u201c.<\/b>\u201d. If name<\/i> refers to a root directory, then the root directory is returned. For example,<\/p>\n file dirname<\/b> c:\/<\/p>\n returns c:\/<\/b>.<\/p>\n Note that tilde substitution will only be performed if it is necessary to complete the command. For example,<\/p>\n file dirname<\/b> ~\/src\/foo.c<\/p>\n returns ~\/src<\/b>, whereas<\/p>\n file dirname<\/b> ~<\/p>\n returns \/home<\/b> (or something similar).<\/p>\n file executable<\/b> name<\/i><\/p>\n Returns 1<\/b> if file name<\/i> is executable by the current user, 0<\/b> otherwise. On Windows, which does not have an executable attribute, the command treats all directories and any files with extensions exe<\/b>, com<\/b>, cmd<\/b> or bat<\/b> as executable.<\/p>\n file exists<\/b> name<\/i><\/p>\n Returns 1<\/b> if file name<\/i> exists and the current user has search privileges for the directories leading to it, 0<\/b> otherwise.<\/p>\n file extension<\/b> name<\/i><\/p>\n Returns all of the characters in name<\/i> after and including the last dot in the last element of name<\/i>. If there is no dot in the last element of name<\/i> then returns the empty string.<\/p>\n file isdirectory<\/b> name<\/i><\/p>\n Returns 1<\/b> if file name<\/i> is a directory, 0<\/b> otherwise.<\/p>\n file isfile<\/b> name<\/i><\/p>\n Returns 1<\/b> if file name<\/i> is a regular file, 0<\/b> otherwise.<\/p>\n file join<\/b> name<\/i> ?name …<\/i>?<\/p>\n Takes one or more file names and combines them, using the correct path separator for the current platform. If a particular name<\/i> is relative, then it will be joined to the previous file name argument. Otherwise, any earlier arguments will be discarded, and joining will proceed from the current argument. For example,<\/p>\n file join<\/b> a b \/foo bar<\/p>\n returns \/foo\/bar<\/b>.<\/p>\n Note that any of the names can contain separators, and that the result is always canonical for the current platform: \/<\/b> for Unix and Windows.<\/p>\n file link<\/b> ?\u2212linktype<\/i>? linkName<\/i> ?target<\/i>?<\/p>\n If only one argument is given, that argument is assumed to be linkName<\/i>, and this command returns the value of the link given by linkName<\/i> (i.e. the name of the file it points to). If linkName<\/i> is not a link or its value cannot be read (as, for example, seems to be the case with hard links, which look just like ordinary files), then an error is returned.<\/p>\n If 2 arguments are given, then these are assumed to be linkName<\/i> and target<\/i>. If linkName<\/i> already exists, or if target<\/i> does not exist, an error will be returned. Otherwise, Tcl creates a new link called linkName<\/i> which points to the existing filesystem object at target<\/i> (which is also the returned value), where the type of the link is platform-specific (on Unix a symbolic link will be the default). This is useful for the case where the user wishes to create a link in a cross-platform way, and does not care what type of link is created.<\/p>\n If the user wishes to make a link of a specific type only, (and signal an error if for some reason that is not possible), then the optional \u2212linktype<\/i> argument should be given. Accepted values for \u2212linktype<\/i> are \u201c\u2212symbolic<\/b>\u201d and \u201c\u2212hard<\/b>\u201d.<\/p>\n On Unix, symbolic links can be made to relative paths, and those paths must be relative to the actual linkName<\/i>\u2019s location (not to the cwd), but on all other platforms where relative links are not supported, target paths will always be converted to absolute, normalized form before the link is created (and therefore relative paths are interpreted as relative to the cwd). Furthermore, \u201c~user\u201d paths are always expanded to absolute form. When creating links on filesystems that either do not support any links, or do not support the specific type requested, an error message will be returned. Most Unix platforms support both symbolic and hard links (the latter for files only). Windows supports symbolic directory links and hard file links on NTFS drives.<\/p>\n file lstat<\/b> name varName<\/i><\/p>\n Same as stat<\/b> option (see below) except uses the lstat<\/i> kernel call instead of stat<\/i>. This means that if name<\/i> refers to a symbolic link the information returned in varName<\/i> is for the link rather than the file it refers to. On systems that do not support symbolic links this option behaves exactly the same as the stat<\/b> option.<\/p>\n file mkdir<\/b> ?dir<\/i> …?<\/p>\n Creates each directory specified. For each pathname dir<\/i> specified, this command will create all non-existing parent directories as well as dir<\/i> itself. If an existing directory is specified, then no action is taken and no error is returned. Trying to overwrite an existing file with a directory will result in an error. Arguments are processed in the order specified, halting at the first error, if any.<\/p>\n file mtime<\/b> name<\/i> ?time<\/i>?<\/p>\n Returns a decimal string giving the time at which file name<\/i> was last modified. If time<\/i> is specified, it is a modification time to set for the file (equivalent to Unix touch<\/b>). The time is measured in the standard POSIX fashion as seconds from a fixed starting time (often January 1, 1970). If the file does not exist or its modified time cannot be queried or set then an error is generated.<\/p>\n file nativename<\/b> name<\/i><\/p>\n Returns the platform-specific name of the file. This is useful if the filename is needed to pass to a platform-specific call, such as to a subprocess via exec<\/b> under Windows (see EXAMPLES<\/b> below).<\/p>\n file normalize<\/b> name<\/i><\/p>\n Returns a unique normalized path representation for the file-system object (file, directory, link, etc), whose string value can be used as a unique identifier for it. A normalized path is an absolute path which has all \u201c..\/\u201d and \u201c.\/\u201d removed. Also it is one which is in the \u201cstandard\u201d format for the native platform. On Unix, this means the segments leading up to the path must be free of symbolic links\/aliases (but the very last path component may be a symbolic link), and on Windows it also means we want the long form with that form\u2019s case-dependence (which gives us a unique, case-dependent path). The one exception concerning the last link in the path is necessary, because Tcl or the user may wish to operate on the actual symbolic link itself (for example file delete<\/b>, file rename<\/b>, file copy<\/b> are defined to operate on symbolic links, not on the things that they point to).<\/p>\n file owned<\/b> name<\/i><\/p>\n Returns 1<\/b> if file name<\/i> is owned by the current user, 0<\/b> otherwise.<\/p>\n file pathtype<\/b> name<\/i><\/p>\n Returns one of absolute<\/b>, relative<\/b>, volumerelative<\/b>. If name<\/i> refers to a specific file on a specific volume, the path type will be absolute<\/b>. If name<\/i> refers to a file relative to the current working directory, then the path type will be relative<\/b>. If name<\/i> refers to a file relative to the current working directory on a specified volume, or to a specific file on the current working volume, then the path type is volumerelative<\/b>.<\/p>\n file readable<\/b> name<\/i><\/p>\n Returns 1<\/b> if file name<\/i> is readable by the current user, 0<\/b> otherwise.<\/p>\n file readlink<\/b> name<\/i><\/p>\n Returns the value of the symbolic link given by name<\/i> (i.e. the name of the file it points to). If name<\/i> is not a symbolic link or its value cannot be read, then an error is returned. On systems that do not support symbolic links this option is undefined.<\/p>\n file rename<\/b> ?\u2212force<\/b>? ?\u2212\u2212<\/b>? source target<\/i> The first form takes the file or directory specified by pathname source<\/i> and renames it to target<\/i>, moving the file if the pathname target<\/i> specifies a name in a different directory. If target<\/i> is an existing directory, then the second form is used. The second form moves each source<\/i> file or directory into the directory targetDir<\/i>. Existing files will not be overwritten unless the \u2212force<\/b> option is specified. When operating inside a single filesystem, Tcl will rename symbolic links rather than the things that they point to. Trying to overwrite a non-empty directory, overwrite a directory with a file, or a file with a directory will all result in errors. Arguments are processed in the order specified, halting at the first error, if any. A \u2212\u2212<\/b> marks the end of switches; the argument following the \u2212\u2212<\/b> will be treated as a source<\/i> even if it starts with a \u2212<\/b>.<\/p>\n file rootname<\/b> name<\/i><\/p>\n Returns all of the characters in name<\/i> up to but not including the last \u201c.\u201d character in the last component of name. If the last component of name<\/i> does not contain a dot, then returns name<\/i>.<\/p>\n file separator<\/b> ?name<\/i>?<\/p>\n If no argument is given, returns the character which is used to separate path segments for native files on this platform. If a path is given, the filesystem responsible for that path is asked to return its separator character. If no file system accepts name<\/i>, an error is generated.<\/p>\n file size<\/b> name<\/i><\/p>\n Returns a decimal string giving the size of file name<\/i> in bytes. If the file does not exist or its size cannot be queried then an error is generated.<\/p>\n file split<\/b> name<\/i><\/p>\n Returns a list whose elements are the path components in name<\/i>. The first element of the list will have the same path type as name<\/i>. All other elements will be relative. Path separators will be discarded unless they are needed to ensure that an element is unambiguously relative. For example, under Unix<\/p>\n file split<\/b> \/foo\/~bar\/baz<\/p>\n returns \u201c\/ foo .\/~bar baz<\/b>\u201d to ensure that later commands that use the third component do not attempt to perform tilde substitution.<\/p>\n file stat<\/b> name varName<\/i><\/p>\n Invokes the stat<\/b> kernel call on name<\/i>, and uses the variable given by varName<\/i> to hold information returned from the kernel call. VarName<\/i> is treated as an array variable, and the following elements of that variable are set: atime<\/b>, ctime<\/b>, dev<\/b>, gid<\/b>, ino<\/b>, mode<\/b>, mtime<\/b>, nlink<\/b>, size<\/b>, type<\/b>, uid<\/b>. Each element except type<\/b> is a decimal string with the value of the corresponding field from the stat<\/b> return structure; see the manual entry for stat<\/b> for details on the meanings of the values. The type<\/b> element gives the type of the file in the same form returned by the command file type<\/b>. This command returns an empty string.<\/p>\n file system<\/b> name<\/i><\/p>\n Returns a list of one or two elements, the first of which is the name of the filesystem to use for the file, and the second, if given, an arbitrary string representing the filesystem-specific nature or type of the location within that filesystem. If a filesystem only supports one type of file, the second element may not be supplied. For example the native files have a first element \u201cnative\u201d, and a second element which when given is a platform-specific type name for the file\u2019s system (e.g. \u201cNTFS\u201d, \u201cFAT\u201d, on Windows). A generic virtual file system might return the list \u201cvfs ftp\u201d to represent a file on a remote ftp site mounted as a virtual filesystem through an extension called \u201cvfs\u201d. If the file does not belong to any filesystem, an error is generated.<\/p>\n file tail<\/b> name<\/i><\/p>\n Returns all of the characters in the last filesystem component of name<\/i>. Any trailing directory separator in name<\/i> is ignored. If name<\/i> contains no separators then returns name<\/i>. So, file tail a\/b<\/b>, file tail a\/b\/<\/b> and file tail b<\/b> all return b<\/b>.<\/p>\n file tempfile<\/b> ?nameVar<\/i>? ?template<\/i>?<\/p>\n Creates a temporary file and returns a read-write channel opened \u2502<\/big> on that file. If the nameVar<\/i> is given, it specifies a variable \u2502<\/big> that the name of the temporary file will be written into; if \u2502<\/big> absent, Tcl will attempt to arrange for the temporary file to be \u2502<\/big> deleted once it is no longer required. If the template<\/i> is \u2502<\/big> present, it specifies parts of the template of the filename to \u2502<\/big> use when creating it (such as the directory, base-name or \u2502<\/big> extension) though some platforms may ignore some or all of these \u2502<\/big> parts and use a built-in default instead. \u2502<\/big><\/p>\n Note that temporary files are only<\/i> ever created on the native \u2502<\/big> filesystem. As such, they can be relied upon to be used with \u2502<\/big> operating-system native APIs and external programs that require \u2502<\/big> a filename. \u2502<\/big><\/p>\n file type<\/b> name<\/i><\/p>\n Returns a string giving the type of file name<\/i>, which will be one of file<\/b>, directory<\/b>, characterSpecial<\/b>, blockSpecial<\/b>, fifo<\/b>, link<\/b>, or socket<\/b>.<\/p>\n file volumes<\/b><\/p>\n Returns the absolute paths to the volumes mounted on the system, as a proper Tcl list. Without any virtual filesystems mounted as root volumes, on UNIX, the command will always return \u201c\/\u201d, since all filesystems are locally mounted. On Windows, it will return a list of the available local drives (e.g. \u201ca:\/ c:\/\u201d). If any virtual filesystem has mounted additional volumes, they will be in the returned list.<\/p>\n file writable<\/b> name<\/i><\/p>\n Returns 1<\/b> if file name<\/i> is writable by the current user, 0<\/b> otherwise.<\/p>\n Unix<\/b><\/p>\n These commands always operate using the real user and group identifiers, not the effective ones.<\/p>\n Windows<\/b><\/p>\n The file owned<\/b> subcommand uses the user identifier (SID) of the process token, not the thread token which may be impersonating some other user.<\/p>\n This procedure shows how to search for C files in a given directory that have a correspondingly-named object file in the current directory:<\/p>\n proc findMatchingCFiles {dir} { Rename a file and leave a symbolic link pointing from the old location to the new place:<\/p>\n set oldName foobar.txt On Windows, a file can be \u201cstarted\u201d easily enough (equivalent to double-clicking on it in the Explorer interface) but the name passed to the operating system must be in native format:<\/p>\n exec {*}[auto_execok start] {} [file nativename<\/b> ~\/example.txt]<\/p>\n filename(n), open(n), close(n), eof(n), gets(n), tell(n), seek(n), fblocked(n), flush(n)<\/p>\n attributes, copy files, delete files, directory, file, move files, name, rename files, stat, user<\/p>\n file \u2212 Manipulate file names and attributes <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3783,1],"tags":[2617,2635],"class_list":["post-6281","post","type-post","status-publish","format-standard","hentry","category-n-comandos-tcl-tk","category-sin-categoria","tag-file","tag-mann"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/6281","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=6281"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/6281\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=6281"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=6281"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=6281"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
SYNOPSIS<\/a>
DESCRIPTION<\/a>
PORTABILITY ISSUES<\/a>
EXAMPLES<\/a>
SEE ALSO<\/a>
KEYWORDS<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
SYNOPSIS <\/a> <\/h2>\n
DESCRIPTION <\/a> <\/h2>\n
file atime<\/b> name<\/i> ?time<\/i>?<\/p>\n
file attributes<\/b> name<\/i> ?option<\/i>?
file attributes<\/b> name<\/i> ?option value option value…<\/i>?<\/p>\n
file copy<\/b> ?\u2212force<\/b>? ?\u2212\u2212<\/b>? source<\/i> ?source<\/i> …? targetDir<\/i><\/p>\n
file rename<\/b> ?\u2212force<\/b>? ?\u2212\u2212<\/b>? source<\/i> ?source<\/i> …? targetDir<\/i><\/p>\nPORTABILITY ISSUES <\/a> <\/h2>\n
EXAMPLES <\/a> <\/h2>\n
set files {}
switch $::tcl_platform(platform) {
windows {
set ext .obj
}
unix {
set ext .o
}
}
foreach file [glob \u2212nocomplain \u2212directory $dir *.c] {
set objectFile [file tail<\/b> [file rootname<\/b> $file]]$ext
if {[file exists<\/b> $objectFile]} {
lappend files $file
}
}
return $files
}<\/p>\n
set newName foo\/bar.txt
# Make sure that where we\u2019re going to move to exists…
if {![file isdirectory<\/b> [file dirname<\/b> $newName]]} {
file mkdir<\/b> [file dirname<\/b> $newName]
}
file rename<\/b> $oldName $newName
file link<\/b> \u2212symbolic $oldName $newName<\/p>\nSEE ALSO <\/a> <\/h2>\n
KEYWORDS <\/a> <\/h2>\n
\n","protected":false},"excerpt":{"rendered":"