Sponsored Content
Homework and Emergencies Homework & Coursework Questions Asst: Using Shell Scripts with sed Post 302878623 by raymondbn on Saturday 7th of December 2013 11:21:48 AM
Old 12-07-2013
Asst: Using Shell Scripts with sed

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!

1. The problem statement, all variables and given/known data:

One problem with the use of sed in simple text substitutions is that sed will intepret some characters as regular expression operators. For example, we might try to change just the punctuation in our earlier example:
echo Hello world. > myFile.txt
~/UnixCourse/scriptAsst/sub1 . ! myFile.txt
cat myFile.txt

and are likely to find
!!!!!!!!!!!!

in myFile.txt instead of the desired "Hello world!".
Create a new script, sub2, taking the three parameters, that treats the string to be replaced as plain text instead of as a regular expression.
The Three parameters :
1.)the string to be replaced
2.)the string with which to replace it
3.)the name of the file in which to make the substitution

Hint 1: Put the target string (the one to be replaced) into a shell variable (e.g., $target). Then use a sed command to rewrite any of the "special" regular expression characters

[ ] ^ * + . $ \ -

into "safe" forms of those same characters by adding backslashes in front (e.g., \*) or surrounding them by [ ] (e.g.,[*]). Store that rewritten version of the target string in in a second shell variable (e.g., $newTarget). Then issue the actual command to perform the substitutions on the file.

Hint 2: For technical reasons, this task is probably easier accomplished in /bin/sh than in /bin/csh. If you insist upon using csh to run your script, you might need to solve this by writing your sed commands into a separate temparary file and using the -f option of sed to run commands from that file.

Again, when you think you have this ready, give the command:

~cs252/bin/scriptAsst.pl

to check your scripts so far.


2. Relevant commands, code, scripts, algorithms:

Unix library

3. The attempts at a solution (include all code and scripts):
my code is:

Code:
#!/bin/sh

echo "$1" , "$2", "$3"

plain=$(echo "$1" | sed "s:[]\[\^\$\.\*\/]:\\&:g")

sed -e "s/$1/$2/g" "$3" >a.out

mv "a.out" "$3"

It seems like "*" is not passing through as a parameter?

error messase:

"sub2 produced incorrect output on test 19: /home/bnaranjo/UnixCourse/scriptAsst/sub2 'l*' 'L' '_king cobra.dat'

Any help is appreciated, thank you!
4. Complete Name of School (University), City (State), Country, Name of Professor, and Course Number (Link to Course):
Old Dominion University, Virginia Beach(VA), USA, Zeil, cs 252

Note: Without school/professor/course information, you will be banned if you post here! You must complete the entire template (not just parts of it).
 

10 More Discussions You Might Find Interesting

1. AIX

Difference between writing Unix Shell script and AIX Shell Scripts

Hi, Please give me the detailed Differences between writing Unix Shell script and AIX Shell Scripts. Thanks in advance..... (0 Replies)
Discussion started by: haroonec
0 Replies

2. Shell Programming and Scripting

number sign(#) in sed scripts

Hi. In a simple sed script i have number signs - #. But i can't find any description on their functionality. One thing that i find is that # in sed scripts can mean comment if it is placed in the beginning of the line. I thought may be this undocumented(for me) behavior refers to regular... (1 Reply)
Discussion started by: kukuruku
1 Replies

3. Shell Programming and Scripting

calling 'n' number of shell scripts based on dependency in one shell script.

Hello gurus, I have three korn shell script 3.1, 3.2, 3.3. I would like to call three shell script in one shell script. i m looking for something like this call 3.1; If 3.1 = "complete" then call 3.2; if 3.2 = ''COMPlete" then call 3.3; else exit The... (1 Reply)
Discussion started by: shashi369
1 Replies

4. Shell Programming and Scripting

sed scripts are not playing nicely!

I am having a lot of trouble, wasting a lot of time trying to get sed script files to run without problem. I have a list of scripts I want to run on a text file to turn it into a viewable html file for my mobile phone. Each of the single scripts when run in order/sequence one after another on the... (4 Replies)
Discussion started by: naphelge
4 Replies

5. Shell Programming and Scripting

Making use of multiple cores for running sed and awk scripts

Hi All, After reading that the sort command in Linux can be made to use many processor cores just by using a simple script which I found on the internet, I was wondering if I can use similar techniques for programs like the awk and sed? #!/bin/bash # Usage: psort filename <chunksize>... (7 Replies)
Discussion started by: shoaibjameel123
7 Replies

6. Shell Programming and Scripting

Help with Shell Scripts Using sed in multiple files.

Hi, I was hoping that someone could help me. I have a problem that i am trying to work on and it requires me to change text within multiple files using sed. I use the program to change an occurance of a word throughout different files that are being tested. At first i had to Create a new script,... (1 Reply)
Discussion started by: Johnny2518
1 Replies

7. Homework & Coursework Questions

Help with Shell Scripts Using sed in multiple files.

Hi, I was hoping that someone could help me. I have a problem that i am trying to work on and it requires me to change text within multiple files using sed. What i have so far is !/bin/sh File1="$3" File2="$4" File3="$5" testNum="$File1" while test "$testNum" <= "$File3"; do echo... (12 Replies)
Discussion started by: Johnny2518
12 Replies

8. UNIX for Dummies Questions & Answers

Rename scripts using xargs/sed

Morning all I've got loads of scripts but the names are too long! I've stuck the list in a flat file (names) and I'm trying to read that in line by line and create the new names (in to directory new) from the list. It looks like this: xargs -n1 -I{} <names cat {} | sed... (1 Reply)
Discussion started by: Grueben
1 Replies

9. Shell Programming and Scripting

Issue with SUNOS running sed scripts

Hi I probably dont have GNU extended sed in my SUNOS . and its creating lot of problems ex: a simple sed command like this is not working sed '/WORD/ a\ sample text line 1 \ sample text line 1 ' filename sed: command garbled: /WORD/ a I took precaution to have a new line after... (11 Replies)
Discussion started by: vash
11 Replies

10. Homework & Coursework Questions

Asst: Shell Script to sed

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: Generalize your sub2 script, producing a new script sub3 that will apply a substitution to any number of files... (16 Replies)
Discussion started by: raymondbn
16 Replies
SED(1)							    BSD General Commands Manual 						    SED(1)

NAME
sed -- stream editor SYNOPSIS
sed [-aEnr] command [file ...] sed [-aEnr] [-e command] [-f command_file] [file ...] DESCRIPTION
The sed utility reads the specified files, or the standard input if no files are specified, modifying the input as specified by a list of commands. The input is then written to the standard output. A single command may be specified as the first argument to sed. Multiple commands may be specified by using the -e or -f options. All com- mands are applied to the input in the order they are specified regardless of their origin. The following options are available: -a The files listed as parameters for the ``w'' functions are created (or truncated) before any processing begins, by default. The -a option causes sed to delay opening each file until a command containing the related ``w'' function is applied to a line of input. -E Enables the use of extended regular expressions instead of the usual basic regular expression syntax. -e command Append the editing commands specified by the command argument to the list of commands. -f command_file Append the editing commands found in the file command_file to the list of commands. The editing commands should each be listed on a separate line. -n By default, each line of input is echoed to the standard output after all of the commands have been applied to it. The -n option suppresses this behavior. -r Identical to -E, present for compatibility with GNU sed. The form of a sed command is as follows: [address[,address]]function[arguments] Whitespace may be inserted before the first address and the function portions of the command. Normally, sed cyclically copies a line of input, not including its terminating newline character, into a pattern space, (unless there is something left after a ``D'' function), applies all of the commands with addresses that select that pattern space, copies the pattern space to the standard output, appending a newline, and deletes the pattern space. Some of the functions use a hold space to save all or part of the pattern space for subsequent retrieval. SED ADDRESSES
An address is not required, but if specified must be a number (that counts input lines cumulatively across input files), a dollar (``$'') character that addresses the last line of input, or a context address (which consists of a regular expression preceded and followed by a delimiter). A command line with no addresses selects every pattern space. A command line with one address selects all of the pattern spaces that match the address. A command line with two addresses selects the inclusive range from the first pattern space that matches the first address through the next pattern space that matches the second. (If the second address is a number less than or equal to the line number first selected, only that line is selected.) Starting at the first line following the selected range, sed starts looking again for the first address. Editing commands can be applied to non-selected pattern spaces by use of the exclamation character (``!'') function. SED REGULAR EXPRESSIONS
The sed regular expressions are basic regular expressions (BRE's, see re_format(7) for more information). In addition, sed has the following two additions to BRE's: 1. In a context address, any character other than a backslash (``'') or newline character may be used to delimit the regular expression by prefixing the first use of that delimiter with a backslash. Also, putting a backslash character before the delimiting character causes the character to be treated literally. For example, in the context address xabcxdefx, the RE delimiter is an ``x'' and the second ``x'' stands for itself, so that the regular expression is ``abcxdef''. 2. The escape sequence matches a newline character embedded in the pattern space. You can't, however, use a literal newline character in an address or in the substitute command. One special feature of sed regular expressions is that they can default to the last regular expression used. If a regular expression is empty, i.e. just the delimiter characters are specified, the last regular expression encountered is used instead. The last regular expres- sion is defined as the last regular expression used as part of an address or substitute command, and at run-time, not compile-time. For example, the command ``/abc/s//XXX/'' will substitute ``XXX'' for the pattern ``abc''. SED FUNCTIONS
In the following list of commands, the maximum number of permissible addresses for each command is indicated by [0addr], [1addr], or [2addr], representing zero, one, or two addresses. The argument text consists of one or more lines. To embed a newline in the text, precede it with a backslash. Other backslashes in text are deleted and the following character taken literally. The ``r'' and ``w'' functions take an optional file parameter, which should be separated from the function letter by white space. Each file given as an argument to sed is created (or its contents truncated) before any input processing begins. The ``b'', ``r'', ``s'', ``t'', ``w'', ``y'', ``!'', and ``:'' functions all accept additional arguments. The following synopses indicate which arguments have to be separated from the function letters by white space characters. Two of the functions take a function-list. This is a list of sed functions separated by newlines, as follows: { function function ... function } The ``{'' can be preceded by white space and can be followed by white space. The function can be preceded by white space. The terminating ``}'' must be preceded by a newline (and optionally white space). [2addr] function-list Execute function-list only when the pattern space is selected. [1addr]a text Write text to standard output immediately before each attempt to read a line of input, whether by executing the ``N'' function or by beginning a new cycle. [2addr]b[label] Branch to the ``:'' function with the specified label. If the label is not specified, branch to the end of the script. [2addr]c text Delete the pattern space. With 0 or 1 address or at the end of a 2-address range, text is written to the standard output. Start the next cycle. [2addr]d Delete the pattern space and start the next cycle. [2addr]D Delete the initial segment of the pattern space through the first newline character and start the next cycle. [2addr]g Replace the contents of the pattern space with the contents of the hold space. [2addr]G Append a newline character followed by the contents of the hold space to the pattern space. [2addr]h Replace the contents of the hold space with the contents of the pattern space. [2addr]H Append a newline character followed by the contents of the pattern space to the hold space. [1addr]i text Write text to the standard output. [2addr]l (The letter ell.) Write the pattern space to the standard output in a visually unambiguous form. This form is as follows: backslash \ alert a form-feed f newline carriage-return tab vertical tab v Nonprintable characters are written as three-digit octal numbers (with a preceding backslash) for each byte in the character (most significant byte first). Long lines are folded, with the point of folding indicated by displaying a backslash followed by a newline. The end of each line is marked with a ``$''. [2addr]n Write the pattern space to the standard output if the default output has not been suppressed, and replace the pattern space with the next line of input. (Does not begin a new cycle.) [2addr]N Append the next line of input to the pattern space, using an embedded newline character to separate the appended material from the original contents. Note that the current line number changes. [2addr]p Write the pattern space to standard output. [2addr]P Write the pattern space, up to the first newline character to the standard output. [1addr]q Branch to the end of the script and quit without starting a new cycle. [1addr]r file Copy the contents of file to the standard output immediately before the next attempt to read a line of input. If file cannot be read for any reason, it is silently ignored and no error condition is set. [2addr]s/regular expression/replacement/flags Substitute the replacement string for the first instance of the regular expression in the pattern space. Any character other than backslash or newline can be used instead of a slash to delimit the RE and the replacement. Within the RE and the replacement, the RE delimiter itself can be used as a literal character if it is preceded by a backslash. An ampersand (``&'') appearing in the replacement is replaced by the string matching the RE. The special meaning of ``&'' in this context can be suppressed by preceding it by a backslash. The string ``#'', where ``#'' is a digit, is replaced by the text matched by the corresponding backreference expression (see re_format(7)). A line can be split by substituting a newline character into it. To specify a newline character in the replacement string, precede it with a backslash. The value of flags in the substitute function is zero or more of the following: 0 ... 9 Make the substitution only for the N'th occurrence of the regular expression in the pattern space. g Make the substitution for all non-overlapping matches of the regular expression, not just the first one. p Write the pattern space to standard output if a replacement was made. If the replacement string is identical to that which it replaces, it is still considered to have been a replacement. w file Append the pattern space to file if a replacement was made. If the replacement string is identical to that which it replaces, it is still considered to have been a replacement. [2addr]t [label] Branch to the ``:'' function bearing the label if any substitutions have been made since the most recent reading of an input line or execution of a ``t'' function. If no label is specified, branch to the end of the script. [2addr]w file Append the pattern space to the file. [2addr]x Swap the contents of the pattern and hold spaces. [2addr]y/string1/string2/ Replace all occurrences of characters in string1 in the pattern space with the corresponding characters from string2. Any character other than a backslash or newline can be used instead of a slash to delimit the strings. Within string1 and string2, a backslash followed by any character other than a newline is that literal character, and a backslash followed by an ``n'' is replaced by a new- line character. [2addr]!function [2addr]!function-list Apply the function or function-list only to the lines that are not selected by the address(es). [0addr]:label This function does nothing; it bears a label to which the ``b'' and ``t'' commands may branch. [1addr]= Write the line number to the standard output followed by a newline character. [0addr] Empty lines are ignored. [0addr]# The ``#'' and the remainder of the line are ignored (treated as a comment), with the single exception that if the first two charac- ters in the file are ``#n'', the default output is suppressed. This is the same as specifying the -n option on the command line. The sed utility exits 0 on success and >0 if an error occurs. SEE ALSO
awk(1), ed(1), grep(1), regex(3), re_format(7) STANDARDS
The sed function is expected to be a superset of the IEEE Std 1003.2 (``POSIX.2'') specification. HISTORY
A sed command appeared in Version 7 AT&T UNIX. BSD
March 17, 2013 BSD
All times are GMT -4. The time now is 07:41 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy