{"id":6148,"date":"2022-12-20T18:57:58","date_gmt":"2022-12-20T21:57:58","guid":{"rendered":"http:\/\/lode.uno\/linux-man\/index.php\/2022\/12\/20\/glob-mann\/"},"modified":"2022-12-20T18:57:58","modified_gmt":"2022-12-20T21:57:58","slug":"glob-mann","status":"publish","type":"post","link":"https:\/\/lode.uno\/linux-man\/2022\/12\/20\/glob-mann\/","title":{"rendered":"glob (mann)"},"content":{"rendered":"

glob<\/h1>\n

NAME<\/a>
SYNOPSIS<\/a>
DESCRIPTION<\/a>
WINDOWS PORTABILITY ISSUES<\/a>
EXAMPLES<\/a>
SEE ALSO<\/a>
KEYWORDS<\/a> <\/p>\n

\n

______________________________________________________________________________<\/p>\n

NAME <\/a> <\/h2>\n

glob \u2212 Return names of files that match patterns<\/p>\n

SYNOPSIS <\/a> <\/h2>\n

glob<\/b> ?switches<\/i>? ?pattern …<\/i>? ______________________________________________________________________________<\/p>\n

DESCRIPTION <\/a> <\/h2>\n

This command performs file name \u201cglobbing\u201d in a fashion similar to the csh shell or bash shell. It returns a list of the files whose names match any of the pattern<\/i> arguments. No particular order is guaranteed in the list, so if a sorted list is required the caller should use lsort<\/b>.<\/p>\n

OPTIONS<\/b>
If the initial arguments to glob<\/b> start with \u2212<\/b> then they are treated as switches. The following switches are currently supported:
\u2212directory<\/b> directory<\/i><\/p>\n

Search for files which match the given patterns starting in the given directory<\/i>. This allows searching of directories whose name contains glob-sensitive characters without the need to quote such characters explicitly. This option may not be used in conjunction with \u2212path<\/b>, which is used to allow searching for complete file paths whose names may contain glob-sensitive characters.<\/p>\n\n\n
<\/td>\n\n

\u2212join<\/b><\/p>\n<\/td>\n

<\/td>\n\n

The remaining pattern arguments, after option processing, are treated as a single pattern obtained by joining the arguments with directory separators.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

\u2212nocomplain<\/b><\/p>\n

Allows an empty list to be returned without error; without this switch an error is returned if the result list would be empty.<\/p>\n

\u2212path<\/b> pathPrefix<\/i><\/p>\n

Search for files with the given pathPrefix<\/i> where the rest of the name matches the given patterns. This allows searching for files with names similar to a given file (as opposed to a directory) even when the names contain glob-sensitive characters. This option may not be used in conjunction with \u2212directory<\/b>. For example, to find all files with the same root name as $path, but differing extensions, you should use \u201cglob \u2212path [file rootname $path] .*<\/b>\u201d which will work even if $path<\/b> contains numerous glob-sensitive characters.<\/p>\n\n\n
<\/td>\n\n

\u2212tails<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Only return the part of each file found which follows the last directory named in any \u2212directory<\/b> or \u2212path<\/b> path specification. Thus \u201cglob \u2212tails \u2212directory $dir *<\/b>\u201d is equivalent to \u201cset pwd [pwd]; cd $dir; glob *; cd $pwd<\/b>\u201d. For \u2212path<\/b> specifications, the returned names will include the last path segment, so \u201cglob \u2212tails \u2212path [file rootname ~\/foo.tex] .*<\/b>\u201d will return paths like foo.aux foo.bib foo.tex<\/b> etc.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

\u2212types<\/b> typeList<\/i><\/p>\n

Only list files or directories which match typeList<\/i>, where the items in the list have two forms. The first form is like the \u2212type option of the Unix find command: b<\/i> (block special file), c<\/i> (character special file), d<\/i> (directory), f<\/i> (plain file), l<\/i> (symbolic link), p<\/i> (named pipe), or s<\/i> (socket), where multiple types may be specified in the list. Glob<\/b> will return all files which match at least one of the types given. Note that symbolic links will be returned both if \u2212types l<\/b> is given, or if the target of a link matches the requested type. So, a link to a directory will be returned if \u2212types d<\/b> was specified.<\/p>\n

The second form specifies types where all the types given must match. These are r<\/i>, w<\/i>, x<\/i> as file permissions, and readonly<\/i>, hidden<\/i> as special permission cases. On the Macintosh, MacOS types and creators are also supported, where any item which is four characters long is assumed to be a MacOS type (e.g. TEXT<\/b>). Items which are of the form {macintosh type XXXX}<\/i> or {macintosh creator XXXX}<\/i> will match types or creators respectively. Unrecognized types, or specifications of multiple MacOS types\/creators will signal an error.<\/p>\n

The two forms may be mixed, so \u2212types {d f r w}<\/b> will find all regular files OR directories that have both read AND write permissions. The following are equivalent:<\/p>\n

glob \u2212type d bodies manpages.csv script_extrae_body.sh script.sh usr
glob *\/<\/b><\/p>\n

except that the first case doesn\u2019t return the trailing \u201c\/\u201d and is more platform independent.<\/p>\n\n\n
<\/td>\n\n

\u2212\u2212<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Marks the end of switches. The argument following this one will be treated as a pattern<\/i> even if it starts with a \u2212<\/b>.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

GLOBBING PATTERNS<\/b>
The pattern<\/i> arguments may contain any of the following special characters, which are a superset of those supported by string match<\/b>:<\/p>\n\n\n\n\n\n\n
<\/td>\n\n

?<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Matches any single character.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

*<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Matches any sequence of zero or more characters.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

[<\/b>chars<\/i>]<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Matches any single character in chars<\/i>. If chars<\/i> contains a sequence of the form a<\/i>\u2212<\/b>b<\/i> then any character between a<\/i> and b<\/i> (inclusive) will match.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

<\/b>x<\/i><\/p>\n<\/td>\n

<\/td>\n\n

Matches the character x<\/i>.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

{<\/b>a<\/i>,<\/b>b<\/i>,<\/b>…<\/i>}<\/p>\n<\/td>\n

<\/td>\n\n

Matches any of the sub-patterns a<\/i>, b<\/i>, etc.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

On Unix, as with csh, a \u201c.\u201d at the beginning of a file\u2019s name or just after a \u201c\/\u201d must be matched explicitly or with a {} construct, unless the \u2212types hidden<\/b> flag is given (since \u201c.\u201d at the beginning of a file\u2019s name indicates that it is hidden). On other platforms, files beginning with a \u201c.\u201d are handled no differently to any others, except the special directories \u201c.\u201d and \u201c..\u201d which must be matched explicitly (this is to avoid a recursive pattern like \u201cglob \u2212join bodies manpages.csv script_extrae_body.sh script.sh usr bodies manpages.csv script_extrae_body.sh script.sh usr bodies manpages.csv script_extrae_body.sh script.sh usr *\u201d from recursing up the directory hierarchy as well as down). In addition, all \u201c\/\u201d characters must be matched explicitly.<\/p>\n

If the first character in a pattern<\/i> is \u201c~\u201d then it refers to the home directory for the user whose name follows the \u201c~\u201d. If the \u201c~\u201d is followed immediately by \u201c\/\u201d then the value of the HOME environment variable is used.<\/p>\n

The glob<\/b> command differs from csh globbing in two ways. First, it does not sort its result list (use the lsort<\/b> command if you want the list sorted). Second, glob<\/b> only returns the names of files that actually exist; in csh no check for existence is made unless a pattern contains a ?, *, or [] construct.<\/p>\n

When the glob<\/b> command returns relative paths whose filenames start with a tilde \u201c~\u201d (for example through glob *<\/b> or glob \u2212tails<\/b>, the returned list will not quote the tilde with \u201c.\/\u201d. This means care must be taken if those names are later to be used with file join<\/b>, to avoid them being interpreted as absolute paths pointing to a given user\u2019s home directory.<\/p>\n

WINDOWS PORTABILITY ISSUES <\/a> <\/h2>\n

For Windows UNC names, the servername and sharename components of the path may not contain ?, *, or [] constructs. On Windows NT, if pattern<\/i> is of the form \u201c~<\/b>username<\/i>@<\/b>domain<\/i>\u201d, it refers to the home directory of the user whose account information resides on the specified NT domain server. Otherwise, user account information is obtained from the local computer.<\/p>\n

Since the backslash character has a special meaning to the glob command, glob patterns containing Windows style path separators need special care. The pattern \u201cC:\\foo\\*<\/i>\u201d is interpreted as \u201cC:foo*<\/i>\u201d where \u201cf<\/i>\u201d will match the single character \u201cf<\/i>\u201d and \u201c*<\/i>\u201d will match the single character \u201c*<\/i>\u201d and will not be interpreted as a wildcard character. One solution to this problem is to use the Unix style forward slash as a path separator. Windows style paths can be converted to Unix style paths with the command \u201cfile join $path<\/b>\u201d or \u201cfile normalize $path<\/b>\u201d.<\/p>\n

EXAMPLES <\/a> <\/h2>\n

Find all the Tcl files in the current directory:<\/p>\n

glob<\/b> *.tcl<\/p>\n

Find all the Tcl files in the user\u2019s home directory, irrespective of what the current directory is:<\/p>\n

glob<\/b> \u2212directory ~ *.tcl<\/p>\n

Find all subdirectories of the current directory:<\/p>\n

glob<\/b> \u2212type d *<\/p>\n

Find all files whose name contains an \u201ca\u201d, a \u201cb\u201d or the sequence \u201ccde\u201d:<\/p>\n

glob<\/b> \u2212type f *{a,b,cde}*<\/p>\n

SEE ALSO <\/a> <\/h2>\n

file(n)<\/p>\n

KEYWORDS <\/a> <\/h2>\n

exist, file, glob, pattern<\/p>\n

\n","protected":false},"excerpt":{"rendered":"

glob \u2212 Return names of files that match patterns <\/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":[1055,2635],"class_list":["post-6148","post","type-post","status-publish","format-standard","hentry","category-n-comandos-tcl-tk","category-sin-categoria","tag-glob","tag-mann"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/6148","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=6148"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/6148\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=6148"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=6148"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=6148"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}