Sponsored Content
Full Discussion: How to get Key codes
Top Forums Programming How to get Key codes Post 13182 by shriram on Sunday 13th of January 2002 02:10:41 PM
Old 01-13-2002
Java

Hi All.
I am still a beginner in Unix.I have got one program.i am not getting the solution for one program.Will anybody help me soon.

Q.write a C program which accepts a valid directory name as a command line argument and list all the files in the given diirectory as well as all the files in subsequent directories.(The solution can be recursive or non-recursive).

I need the solution immediately.I need it desperately within 15th Jan.
 

8 More Discussions You Might Find Interesting

1. Programming

exit codes

Where can a locate a list of Unix exit codes? thank you, Donna (3 Replies)
Discussion started by: donna carter
3 Replies

2. UNIX for Dummies Questions & Answers

Help with Return codes

I have the below script I am running on a Solaris system to check the status of a Tivoli Workload Scheduler job and return the status. We need this script to return a '0' if any of the jobs in the stream are in a "EXEC" state and an "1" if in a "HOLD" state. I am not a programmer so I am not sure... (1 Reply)
Discussion started by: leezer1204
1 Replies

3. Cybersecurity

SSH key code versus server key code

Hi, When logging in using SSH access (to a remotely hosted account), I received a prompt to accept a server's key fingerprint. Wrote that string of code down for comparision. Already emailed my host for their listing of the string of code for the server's key fingerprint (for comparison,... (1 Reply)
Discussion started by: Texan
1 Replies

4. UNIX for Advanced & Expert Users

Return Codes

I have a simple script which renames a file.How do i capture the return code of the script if the script fails (3 Replies)
Discussion started by: kris01752
3 Replies

5. UNIX for Dummies Questions & Answers

Pressing backspace key simulates enter key

Hi, Whenever i press the backspace key, a new line appears, i.e. it works like a enter key. :confused: Thanks (2 Replies)
Discussion started by: vibhor_agarwali
2 Replies

6. AIX

Warning codes

Dear Experts, i am very to AIX when i am trying to compile my code i am getting two warning several times like 1540-0053 (W) The declaration of a class member within the class definition must not be qualified. "/usr/include/alloca.h", line 34.9: 1540-1401 (I) An unknown "pragma __alloca" is... (1 Reply)
Discussion started by: vin_pll
1 Replies

7. Solaris

Solaris 8 ssh public key authentication issue - Server refused our key

Hi, I've used the following way to set ssh public key authentication and it is working fine on Solaris 10, RedHat Linux and SuSE Linux servers without any problem. But I got error 'Server refused our key' on Solaris 8 system. Solaris 8 uses SSH2 too. Why? Please help. Thanks. ... (1 Reply)
Discussion started by: aixlover
1 Replies

8. Shell Programming and Scripting

Shell Script @ Find a key word and If the key word matches then replace next 7 lines only

Hi All, I have a XML file which is looks like as below. <<please see the attachment >> <?xml version="1.0" encoding="UTF-8"?> <esites> <esite> <name>XXX.com</name> <storeId>10001</storeId> <module> ... (4 Replies)
Discussion started by: Rajeev_hbk
4 Replies
glob(n) 						       Tcl Built-In Commands							   glob(n)

__________________________________________________________________________________________________________________________________________________

NAME
glob - Return names of files that match patterns SYNOPSIS
glob ?switches? pattern ?pattern ...? _________________________________________________________________ DESCRIPTION
This command performs file name ``globbing'' in a fashion similar to the csh shell. It returns a list of the files whose names match any of the pattern arguments. If the initial arguments to glob start with - then they are treated as switches. The following switches are currently supported: | -directory directory | Search for files which match the given patterns starting in the given directory. 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 -path, which is used to allow searching for complete file paths whose names may contain glob-sensitive characters. | -join | The remaining pattern arguments are treated as a single pattern obtained by joining the arguments with directory separators. -nocomplain Allows an empty list to be returned without error; without this switch an error is returned if the result list would be empty. | -path pathPrefix | Search for files with the given pathPrefix 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 -directory. For example, to find all files with the same root name as $path, but differing | extensions, you should use glob -path [file rootname $path] .* which will work even if $path contains numerous glob-sensitive char- | acters. | -tails | Only return the part of each file found which follows the last directory named in any -directory or -path path specification. Thus | glob -tails -directory $dir * is equivalent to set pwd [pwd] ; cd $dir ; glob *; cd $pwd. For -path specifications, the returned | names will include the last path segment, so glob -tails -path [file rootname ~/foo.tex] .* will return paths like foo.aux foo.bib | foo.tex etc. | -types typeList | Only list files or directories which match typeList, where the items in the list have two forms. The first form is like the -type | option of the Unix find command: b (block special file), c (character special file), d (directory), f (plain file), l (symbolic | link), p (named pipe), or s (socket), where multiple types may be specified in the list. Glob will return all files which match at | least one of the types given. | The second form specifies types where all the types given must match. These are r, w, x as file permissions, and readonly, hidden | 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). Items which are of the form {macintosh type XXXX} or {macintosh creator XXXX} will | match types or creators respectively. Unrecognized types, or specifications of multiple MacOS types/creators will signal an error. | The two forms may be mixed, so -types {d f r w} will find all regular files OR directories that have both read AND write permis- | sions. The following are equivalent: | glob -type d * | glob */ | except that the first case doesn't return the trailing ``/'' and is more platform independent. | -- Marks the end of switches. The argument following this one will be treated as a pattern even if it starts with a -. The pattern arguments may contain any of the following special characters: ? Matches any single character. * Matches any sequence of zero or more characters. [chars] Matches any single character in chars. If chars contains a sequence of the form a-b then any character between a and b (inclu- sive) will match. x Matches the character x. {a,b,...} Matches any of the strings a, b, etc. On Unix, as with csh, a ``.'' at the beginning of a file's name or just after a ``/'' must be matched explicitly or with a {} construct, unless the ``-types hidden'' flag is given (since ``.'' at the beginning of a file's name indicates that it is hidden). On other plat- forms, files beginning with a ``.'' are handled no differently to any others, except the special directories ``.'' and ``..'' which must be matched explicitly (this is to avoid a recursive pattern like ``glob -join * * * *'' from recursing up the directory hierarchy as well as down). In addition, all ``/'' characters must be matched explicitly. If the first character in a pattern is ``~'' then it refers to the home directory for the user whose name follows the ``~''. If the ``~'' is followed immediately by ``/'' then the value of the HOME environment variable is used. The glob command differs from csh globbing in two ways. First, it does not sort its result list (use the lsort command if you want the list sorted). Second, glob only returns the names of files that actually exist; in csh no check for existence is made unless a pattern contains a ?, *, or [] construct. PORTABILITY ISSUES
Unlike other Tcl commands that will accept both network and native style names (see the filename manual entry for details on how native and network names are specified), the glob command only accepts native names. Windows For Windows UNC names, the servername and sharename components of the path may not contain ?, *, or [] constructs. On Windows NT, if pattern is of the form ``~username@domain'' 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. On Windows 95 and 98, glob accepts patterns like ``.../'' and ``..../'' for successively higher up parent directories. Since the backslash character has a special meaning to the glob command, glob patterns containing Windows style path separators need special care. The pattern C:\foo\* is interpreted as C:foo* where f will match the single character f and * will match the single character * and will not be interpreted as a wildcard character. One solution to this problem is to use the Unix style for- ward slash as a path separator. Windows style paths can be converted to Unix style paths with the command file join $path (or file normalize $path in Tcl 8.4). Macintosh When using the options, -directory, -join or -path, glob assumes the directory separator for the entire pattern is the standard ``:''. When not using these options, glob examines each pattern argument and uses ``/'' unless the pattern contains a ``:''. SEE ALSO
file(n) KEYWORDS
exist, file, glob, pattern Tcl 8.3 glob(n)
All times are GMT -4. The time now is 06:07 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy