Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: puting arguments into varables
Top Forums Shell Programming and Scripting puting arguments into varables Post 302196273 by Franklin52 on Saturday 17th of May 2008 01:41:17 PM
Old 05-17-2008
An example how to shift the parameters:

Code:
#!/bin/sh

n=$(( $# - 1 ))

for i in `seq 1 $n`
do
  s=$s" $i"
  shift
done

echo Line: "$s"
echo Name: "$1"

And one with sed:

Code:
#!/bin/sh

line=$(echo "$*"|sed 's/\(.*\) .*/\1/')
name=$(echo "$*"|sed 's/.* \(.*\)/\1/')

echo Line " "$line"
echo Name " "$name"

 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Arguments

Ok so i had to create a file and put some random text into it which i did. THen u make a script which takes 2 arguments. The first being a line of text, the second being your newly created file. The script should take the first argument and insert it into the very top (the first line) of... (1 Reply)
Discussion started by: iago
1 Replies

2. Shell Programming and Scripting

[: too many arguments

Hi Guys I have this small Bash script - but it fails when I'm trying to run it. ./test.sh: && ; then # date >> /writable/sys/shutdown.log shutdown -h "now" exit fi done (4 Replies)
Discussion started by: tainted2real
4 Replies

3. Shell Programming and Scripting

Help puting background process ID's into an array

I am trying to write a script that runs another script consecutively and records the PID of the called script each time it runs in an array. I put in an echo statement to check the PID, when the script runs no PID is output, and the array seems to be empty. I assume it is problem with my code,... (3 Replies)
Discussion started by: Breakology
3 Replies

4. Shell Programming and Scripting

while puting shell variable in mysql command value does not interpolate

port=$(ssh tms6@$x cat /tms6/scripts/start.lc.sh | grep -P '^\/tms6\/bin\/lc' | cut -d' ' -f3 | cut -b 3-6) tpsip=$(ssh tms6@$x cat /tms6/scripts/start.lc.sh | grep -P '^\/tms6\/bin\/lc' | cut -d' ' -f4 | cut -b 9-) # IFS="\n" set -- $port ... (1 Reply)
Discussion started by: rrd1986
1 Replies

5. Shell Programming and Scripting

grep with two arguments to arguments to surch for

Hello, is it possible to give grep two documents to surche for? like grep "test" /home/one.txt AND /home/two.txt ? thanks (1 Reply)
Discussion started by: Cybertron
1 Replies

6. Shell Programming and Scripting

: [: too many arguments in for -f in if

Hi Experts , I have following code if ; then mv path /filename newdirpath echo "K* files moved successfully to newdirpath \n" else echo "K* files DID NOT moved successfully to newdirpath \n" fi I am getting "echo "K* files DID NOT moved successfully to newdirpath \n"... (19 Replies)
Discussion started by: ajaypatil_am
19 Replies

7. Shell Programming and Scripting

For f in * -- too many arguments

Hi guys, I am trying to make a script that will archive all the folders (except NOARCHIVE folder) and then remove those folders: cd my_specific_folder; for f in *; do if ; then tar czf $f.tar.gz $f && rm -r $f; fi; done && echo "All the folders within my_specific_folder are... (3 Replies)
Discussion started by: emanresu
3 Replies

8. Ubuntu

Sudo commands without puting in .bashrc

dear all, When I start my laptop, I need to run one command /etc/init.open-afs start and it require sudo privilege. The only solution which occur to me is to put this command in .bashrc. But then the trouble comes as everytime I open any new tab it ask for the sudo password, which is pretty... (5 Replies)
Discussion started by: emily
5 Replies

9. Shell Programming and Scripting

Too many arguments

because it gives me this error if? while read linea do #echo "Archivos Entrada: $linea" largo=`awk '{print length($linea)}'` echo "largo : $largo " if ; then #Here's the problem, I take this line and it works echo "a es igual a 1" fi... (3 Replies)
Discussion started by: tricampeon81
3 Replies

LEARN ABOUT OSX

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
All times are GMT -4. The time now is 12:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy