11-06-2018
Hi Folks,
A clear misunderstanding of the word "concatenate" on my part;-)
Regards
Gull04
10 More Discussions You Might Find Interesting
1. Programming
Hi,
Am supposed to use message queues to send and receive messages between the processes. when i was working on that i realised that the message qid and the message queue related data should be maintained in a shared memory so that it can be accessed by all the processes. Could anybody refer... (10 Replies)
Discussion started by: rvan
10 Replies
2. Shell Programming and Scripting
I am trying to write a script that will help me put a file into excel with little manipulation. Below is a sample of the file im using.
Group1:*:gid1:user,user
Group2:*:gid2:user,user
Group3:*:gid3:user,user,user,user,user,user,user
Group4:*:gid4:user,user
I marked in red the part that is... (1 Reply)
Discussion started by: rookieuxixsa
1 Replies
3. Shell Programming and Scripting
Hello all, I have been asked to exercise my shell scripting and it has been 10 plus years since I used to do it so I can not remember hardly anything and ask for your help.
What I need to do is copy a line out of a file that can be 10 to 100 characters long, I then need to parse this line into... (3 Replies)
Discussion started by: Alivadoro
3 Replies
4. Shell Programming and Scripting
I have a file with data records separated by multiple equals signs, as below.
==========
RECORD 1
==========
RECORD 2
DATA LINE
==========
RECORD 3
==========
RECORD 4
DATA LINE
==========
RECORD 5
DATA LINE
==========
I need to filter out all data from this file where the... (2 Replies)
Discussion started by: Finja
2 Replies
5. Shell Programming and Scripting
i have to remove the commented (/* . . . .*/) part which starts in one line and ends in other.help me with generic code because i have 1000 to 10k lines code which i have to remove.
data one;
set work.temp;
input name age;
infile filename;
/* dfsdf
dsfs
sdfdf
dsdd
sdfsf
sdfsf
sfs... (4 Replies)
Discussion started by: saaisiva
4 Replies
6. Shell Programming and Scripting
It looks like if matching and deleting the last line confuses 'sed' so it does not recognize '$' address. Consider:
sed -e '/^3/d' -e '$ a text'
supposed to delete a line starting with '3' and then append 'text' after the last line of input. But, if it is the last line of input which starts... (2 Replies)
Discussion started by: msz59
2 Replies
7. Shell Programming and Scripting
Hello,
Currently, I am reading few queries from the below .sql file
--SOURCE TABLE NAME
--SOURCE QUERY
SEL COL1, COL2, COL3, COL4,
COL5, COL6, COL7 WHERE COL5 = '2015-11-04 16:24:00.000000' FROM SOURCE TABLE;
--TARGET TABLE NAME
--TARGET QUERY
SEL COLUMN1, COLUMN2, COLUMN3, COLUMN4,... (4 Replies)
Discussion started by: ronitreddy
4 Replies
8. UNIX for Beginners Questions & Answers
Hi there,
I'm trying to create a script that will accept multiple inputs by copying and pasting the strings from a notepad, hit Enter key and output the string to a text file.I'm thinking of using the read command however it will just simply get the first line.
Apologies but got no idea how... (7 Replies)
Discussion started by: norbie.lopez
7 Replies
9. Shell Programming and Scripting
Input File:
>Seq1
ASDADAFASFASFADGSDGFSDFSDFSDFSDFSDFSDFSDFSDFSDFSDFSD
>Seq2
SDASDAQEQWEQeqAdfaasd
>Seq3
ASDSALGHIUDFJANCAGPATHLACJHPAUTYNJKG
......
Desired Output File
>Seq1
ASDADAFASF
ASFADGSDGF
SDFSDFSDFS
DFSDFSDFSD
FSDFSDFSDF
SD
>Seq2 (4 Replies)
Discussion started by: patrick87
4 Replies
10. UNIX for Beginners Questions & Answers
Hi,
Can anyone help me for merge the following multi-line log which beginning with a " and line ending with ": into one line.
*****Original Log*****
087;2008-12-06;084403;"mc;;SYHLR6AP1D\LNZW;AD-703;1;12475;SYHLR6AP1B;1.1.1.1;0000000062;HGPDI:MSISDN=12345678,APNID=1,EQOSID=365;... (3 Replies)
Discussion started by: rajeshlinux2010
3 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