Sponsored Content
Full Discussion: <LF> versus <CR>/<LF>
Top Forums Shell Programming and Scripting <LF> versus <CR>/<LF> Post 87135 by jerardfjay on Thursday 20th of October 2005 10:26:14 AM
Old 10-20-2005
<LF> versus <CR>/<LF>

Hello,

Can someone explain how to distinguish a LF character and a CR/LF character in a text file from a shell script.

Thanks

Last edited by jerardfjay; 10-20-2005 at 02:27 PM.. Reason: question was incorrect (changed CR to LF)
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

CTRL+H versus ^? versus BACKSPACE

Hi Gurus! I recently got my shell account (HP UX v11) created by our sysadmin and am having problem deleting with the backspace key. After doing some reading, I believe I need to enter a custom "STTY..." statement in my profile. Can someone please help me with the correct "STTY" sequence... (3 Replies)
Discussion started by: alan
3 Replies

2. AIX

AIX versus Networks

HI folks, Actually i have a network engineer having 2 and 1/2 years of experience in cisco having CCNA certification also. Now my company offering me to move to AIX field. I am new to AIX and do not know more about that field. So i want a suggestion from you peoples, that I have to join AIX or... (5 Replies)
Discussion started by: rawatmohinder
5 Replies

3. UNIX for Advanced & Expert Users

cpio versus cp

I am copying a file system to another one. someone suggest me use find . -print |cpio -pdmv but I think cp -r should do the same thing. Am I right? In addition, by using " find . ", I got all the file names,, why do I have to use the -print option? Thanks a lot! (1 Reply)
Discussion started by: fredao
1 Replies

4. Shell Programming and Scripting

.chsrc Versus .login

All, I am trying to understand the difference between .login & .cshrc. My understanding here is, there is not much difference between .cshrc and .login. Both the files accomplish the same purpose. But the calling order is different. The .login file called only when you login after calling .cshrc... (1 Reply)
Discussion started by: govindts
1 Replies

5. Shell Programming and Scripting

Awk Versus Cut

Hello ALL, I am looking for a comparison in 2 commands using awk and cut that would replicate the following command below. This is completely for speed reasons checking apache logs for unique IPs. Contender #1 awk '{!a++}END{for(i in a) if ( a >10 ) print a,i }' access_log I need a... (6 Replies)
Discussion started by: jaysunn
6 Replies

6. Shell Programming and Scripting

Bourne sh versus bash

Hi All, I know difference between shell(s) we are using, ie. sh, bash etc. But while writing shell script, is there any difference which shell I am using. and if yes, what are they? (4 Replies)
Discussion started by: Deei
4 Replies

7. Solaris

Solaris versus Centos

hi guys In a few days I will be working in a new Job my new chief told I will be using Solaris and since I know Centos-Red Hat-Fedora I would like to know if Solaris is that different from Centos and my other linux Flavors... by the way any good solaris manual thanks a lot (1 Reply)
Discussion started by: karlochacon
1 Replies

8. SCO

Printing via hpnpf versus lp

Hi, We have a Unix 3.2v5.0.5. I installed a printer via scoadmin, HP network printer manager with network peripheral name an ip-adress. This is the configuration file : Code: root@sco1 # cat configurationBanner: on:AlwaysContent types: simpleDevice: /dev/null Interface:... (2 Replies)
Discussion started by: haezeban
2 Replies
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
All times are GMT -4. The time now is 04:40 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy