01-10-2008
don't know how to implentment as unix sh script
for each file if file name like xx*
for each line in a file
if substring(3,6) found in another txt file[ the file just have 1 column but have multiple line]
output to file-a( filename = orginal file + _a)
else
output to file-b( filename = orginal file + _a)
end
Next Line
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I want to cheaply build my own PC that will run the latest versions of Linspire, Fedora Core, FreeBSD and Solaris, but I don't know where to start.
This PC doesn't have to be particulary fast. It's video performance need not be top notch, however, sound quality and sound performance must rock!... (4 Replies)
Discussion started by: Mr. Nice Guy
4 Replies
2. UNIX for Dummies Questions & Answers
Iīm struggling to find a system I like and thatīs not to overwhelming.. Iīve been using Ubuntu/Linux and itīs allright except that itīs pretty buggy and boots extremely slow. Iīm in need of a system that offers good programming features, simple or no x server, fast to boot and STABLE. Donīt care... (2 Replies)
Discussion started by: riwaTNT
2 Replies
3. UNIX for Dummies Questions & Answers
I use Mac OSX and have been given all of my video editing software... illegally. I don't want to use it anymore and heard that Unix was the way to go. So that is why I am here. What video editing software is out there for Unix. I think I have Unix. Do I?
I am sorry and if all anyone can... (0 Replies)
Discussion started by: moz1979
0 Replies
4. Programming
gcc works find in my Unix. But when I want to use cc1, system reports:
"bash: cc1: command not found". Any clue? Thank you! (2 Replies)
Discussion started by: meili100
2 Replies
5. Shell Programming and Scripting
Hello everybody!
I am new to this and I am trying to change a script in an open source program that plots some offset vectors and then calls a postscript viewer. I have commented away the call for the postscript viewer but somehow the script doesn't return to the shell prompt. I cant figure out... (3 Replies)
Discussion started by: larne
3 Replies
6. UNIX for Advanced & Expert Users
if {"$my_ext_type" = MAIN]; then
cd $v_sc_dir
Filex.SH $v_so_dir\/$v_fr_file
Can somebody tell me what does this suggest. I am pretty new to unix and
I am getting confused.
What i understood from here is
If we have a file extension name as MAIN
which we have then we change the directory to... (1 Reply)
Discussion started by: pochaman
1 Replies
7. Filesystems, Disks and Memory
Hi
I am wondering which is the reason why there is no need to defrag file system in UNIX and Linux, and in Windows I must defrag it ? (7 Replies)
Discussion started by: solaris_user
7 Replies
8. UNIX for Dummies Questions & Answers
Hi,
A file is transferred from a Windows server(say username : user1) to Unix server via ftp.
In unix, the permission of the file for a user, say user2 will be "-rw-r-----". Since the user1 is the owner of the file, user2 is not able to change the file permission using chmod.
Is there... (5 Replies)
Discussion started by: merin
5 Replies
9. Shell Programming and Scripting
Hi Guys,
I am very new to shell script and I need your help here to write a script. Actually, I have a script abc.sh which don't get terminated itself. So I need to design a script to run this script, save the output to a file, search for a given string in the output and if it exists send those... (11 Replies)
Discussion started by: Sambit Sahu
11 Replies
LEARN ABOUT MOJAVE
osacompile
OSACOMPILE(1) BSD General Commands Manual OSACOMPILE(1)
NAME
osacompile -- compile AppleScripts and other OSA language scripts
SYNOPSIS
osacompile [-l language] [-e command] [-o name] [-d] [-r type:id] [-t type] [-c creator] [-x] [-s] [-u] [-a arch] [file ...]
DESCRIPTION
osacompile compiles the given files, or standard input if none are listed, into a single output script. Files may be plain text or other
compiled scripts. The options are as follows:
-l language
Override the language for any plain text files. Normally, plain text files are compiled as AppleScript.
-e command
Enter one line of a script. Script commands given via -e are prepended to the normal source, if any. Multiple -e options may be given
to build up a multi-line script. Because most scripts use characters that are special to many shell programs (e.g., AppleScript uses
single and double quote marks, ``('', ``)'', and ``*''), the command will have to be correctly quoted and escaped to get it past the
shell intact.
-o name
Place the output in the file name. If -o is not specified, the resulting script is placed in the file ``a.scpt''. The value of -o
partly determines the output file format; see below.
-x Save the resulting script as execute-only.
The following options are only relevant when creating a new bundled applet or droplet:
-s Stay-open applet.
-u Use startup screen.
-a arch
Create the applet or droplet for the specified target architecture arch. The allowable values are ``ppc'', ``i386'', and ``x86_64''.
The default is to create a universal binary.
The following options control the packaging of the output file. You should only need them for compatibility with classic Mac OS or for cus-
tom file formats.
-d Place the resulting script in the data fork of the output file. This is the default.
-r type:id
Place the resulting script in the resource fork of the output file, in the specified resource.
-t type
Set the output file type to type, where type is a four-character code. If this option is not specified, the creator code will not be
set.
-c creator
Set the output file creator to creator, where creator is a four-character code. If this option is not specified, the creator code will
not be set.
If no options are specified, osacompile produces a Mac OS X format script file: data fork only, with no type or creator code.
If the -o option is specified and the file does not already exist, osacompile uses the filename extension to determine what type of file to
create. If the filename ends with ``.app'', it creates a bundled applet or droplet. If the filename ends with ``.scptd'', it creates a bun-
dled compiled script. Otherwise, it creates a flat file with the script data placed according to the values of the -d and -r options.
EXAMPLES
To produce a script compatible with classic Mac OS:
osacompile -r scpt:128 -t osas -c ToyS example.applescript
SEE ALSO
osascript(1), osalang(1)
Mac OS X November 12, 2008 Mac OS X