Sponsored Content
Full Discussion: Wildcards In UNIX
Top Forums UNIX for Dummies Questions & Answers Wildcards In UNIX Post 13175 by smdakram on Sunday 13th of January 2002 07:09:29 AM
Old 01-13-2002
Data Wildcards In UNIX

on my SCO UNIX wild cards are not displaying wanted result.
Why like that . I think that i was not using proper command .

what are there . how can i use the wildcards in UNIX.
 

10 More Discussions You Might Find Interesting

1. Programming

Makefile wildcards

Using a makefile I want to compile all .c files in the current directory without specifying them directly and then link their associated .o files into a library. How do I do this ? Thanks. (1 Reply)
Discussion started by: rcscott
1 Replies

2. UNIX for Dummies Questions & Answers

ls - wildcards and global use

Hiya, I want to list all files missing a certain pattern and/or filename pattern on the entire drive. In DOS I would type (for instance): dir \t*.doc /s /a which should find all doc files whose filename starts with `t'. How do I do that in a unix shell? Can it be done w/ ls at... (5 Replies)
Discussion started by: ropers
5 Replies

3. UNIX for Dummies Questions & Answers

Wildcards in VI

I'm trying to delete lines from a large text file using VI. Every line that I am wanting to delete start with 'S' - all others do not. (A list of users) I've tried using * but doesn't seem to like it...any ideas... Doesn't have to be VI - but I'm better with VI than sed/awk. (8 Replies)
Discussion started by: peter.herlihy
8 Replies

4. UNIX for Dummies Questions & Answers

wildcards

when writing a shell script (bourne) and using a unix command like 'ls' is there anything special you need to do to use a wildcard (like *)? (3 Replies)
Discussion started by: benu302000
3 Replies

5. UNIX for Dummies Questions & Answers

ls with wildcards

ok, I'm trying to write a script file that lists files with specific elements in the name into a txt file, it looks like this ls s*.dat > file_names.txt can't figure out whats wrong with that line, any ideas? thanks in advance (10 Replies)
Discussion started by: benu302000
10 Replies

6. UNIX for Dummies Questions & Answers

wildcards NOT

Hi All Please excuse another straightforward question. When creating a tar archive from a directory I am attempting to use wildcards to eliminate certain filetypes (otherwise the archive gets too large). So I am looking for something along these lines. tar -cf archive.tar * <minus all *.rst... (5 Replies)
Discussion started by: C3000
5 Replies

7. UNIX for Dummies Questions & Answers

wildcards in path

Is there some rule about using wildcards in path? Say I want to create a file, but one of the directories in the path is called 1433d.default and on different machines it will be called <some other string>.default touch ~/Library/Application/*.default/myfile In theory I thought that... (5 Replies)
Discussion started by: glev2005
5 Replies

8. UNIX for Advanced & Expert Users

Wildcards

These 2 websites do a GREAT job of explaining different types of wildcards. I learned about the categories of characters which I never knew about at all. GNU/Linux Command-Line Tools Guide - Wildcards GREP (1 Reply)
Discussion started by: cokedude
1 Replies

9. Shell Programming and Scripting

Wildcards and exceptions

Hello: I have a very basic question. I'd like to select all files except for one file. For example, say I want to move all of the files in my current directory to a subdirectory called archive, I would use mv ./* archive/ But what if I want to move all files except for README.txt? Is there an... (19 Replies)
Discussion started by: Danny.Boy
19 Replies

10. UNIX for Dummies Questions & Answers

Renaming with wildcards

Hi, I'm new to Unix, but have a directory which has many files in it, well over 1000. The files are called : M07GO.STOPE0001 M07GO.STOPE0002 M07GO.STOPE0003 M07GO.STOPE0004 etc... I would like to rename them to the following : M070001.bin M070002.bin M070003.bin M070004.bin etc....... (4 Replies)
Discussion started by: rnmuk
4 Replies
standards(5)							File Formats Manual						      standards(5)

NAME
standards - UNIX standards behavior on HP-UX DESCRIPTION
HP-UX conforms to various UNIX standards. In some cases, these standards conflict. This manpage describes the methods that programmers and users must follow to have an application conform and execute according to a particular UNIX standard. UNIX Standard Conformant Programmer Environment The following table lists feature test macros and environment variables that must be defined while compiling an application. Both a fea- ture test macro and an environment variable must be defined while compiling the application so that the application conforms and executes according to a particular UNIX standard. Otherwise, the behavior is undefined. Standard Feature Test Macros to be Environment variable defined during compilation to be set UNIX 95 _XOPEN_SOURCE_EXTENDED=1 UNIX95 or UNIX_STD=95 or UNIX_STD=1995 UNIX 2003 _XOPEN_SOURCE=600 UNIX_STD=2003 The compiler uses the feature test macros to obtain the appropriate namespace from the header files. The compiler uses the environment variable to link in an appropriate object file to the executable. Using the environment variable customizes libc to match UNIX standards for various functions. If an application has already been compiled for default HP-UX behavior or for one particular standard, and needs to change to a particular UNIX standard behavior, recompile the application as specified in the above table. For an HP-UX command to conform to a particular UNIX standard behavior, the application has to set the corresponding environment variable as specified in the above table before executing that command. UNIX Standard Conformant User Environment To enable a particular UNIX standard conformant user environment, set the corresponding environment variable as defined in the above table. EXAMPLES
The following examples shows an application example. To have the system be conformant to UNIX2003 behavior, set the environment variable to and define the feature test macro before compilation. The following example changes the command to have UNIX95 behavior by setting one of the environment variables to or to before executing that command. There are three ways of setting the environment variable for UNIX95: or or SEE ALSO
cc(1), stdsyms(5). standards(5)
All times are GMT -4. The time now is 03:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy