Sponsored Content
Full Discussion: strange sed behavior
Top Forums UNIX for Dummies Questions & Answers strange sed behavior Post 37086 by Perderabo on Thursday 12th of June 2003 06:43:49 AM
Old 06-12-2003
If you have accurately described the situation, your version of sed has a bug. Complain to your vendor.

However, note that sed is line based. A line is a sequence of characters followed by a newline character. The last character of your file must be a newline character. If this is not the case, the results are undefined and both versions of sed are working correctly.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Strange Behavior on COM2

Hi, I have a problem with a new touch screen controller that I am trying to use on a SCO 3.0 system. THe touch screen controller only wants to talk at 9600baud. I have updated /etc/inittab per the manual and also edited /usr/lib/event/devices to use 9600 baud. The only way I can get the... (0 Replies)
Discussion started by: Elwood51
0 Replies

2. Shell Programming and Scripting

Very Strange Behavior for redirection

I have searched far and wide for an explanation for some odd behavior for output redirection and haven't come up with anything. A co-worker was working on old scripts which have run for years and embedded in their code were output redirects which worked for the script during execution and then... (5 Replies)
Discussion started by: cahook
5 Replies

3. Shell Programming and Scripting

nawk strange behavior

Dear guys; when deleting repeated lines using nawk as below ; Why the below syntax works? nawk ' !a++' infile > outfile and when using the other below syntax the nawk doesn't work? nawk ' { !a++ } ' infile > outfile or nawk ' { !a++ } ' infile > outfile BR (4 Replies)
Discussion started by: ahmad.diab
4 Replies

4. Shell Programming and Scripting

sed strange quotes behavior

Hi gurus input file: 1 2 3 4 desired output 1 2\ 2a 3 4 I tried (6 Replies)
Discussion started by: wakatana
6 Replies

5. Programming

Strange behavior in C++

I have the following program: int main(int argc, char** argv){ unsigned long int mean=0; for(int i=1;i<10;i++){ mean+=poisson(12); cout<<mean<<endl; } cout<<"Sum of poisson: "<< mean; return 0; } when I run it, I get the... (4 Replies)
Discussion started by: santiagorf
4 Replies

6. Ubuntu

Ubuntu strange behavior

It is so till login screen. I mean that when I boot my computer, Ubuntu shows a splash screen with mouse instead of Ubuntu logo and in the login screen it shows XUbuntu login screen... It began when I upgraded to previous kernel, I suppose, but I'm not sure... I can't say that it annoys me very... (6 Replies)
Discussion started by: Sapfeer
6 Replies

7. Red Hat

strange mail behavior

Hi I have script to to take backup and send mail to a group once a day. One strange behavior I have observed recently is that most of the time the mail we receive is fine . But someday it just sends out mail without any subject with undisclosed recipients. I dont know how to find the cause... (0 Replies)
Discussion started by: ningy
0 Replies

8. Shell Programming and Scripting

Strange behavior on one of my server

I am not sure what is wrong, but I have some strange behavior when printing things out. I do create a file with only one word test, no space, no new line etc. nano file<enter> test<ctrl x>y<enter> Server 1 gets (fail) awk '{print "+"$0"*"}' file *test Server 2 gets (OK) awk '{print... (9 Replies)
Discussion started by: Jotne
9 Replies

9. AIX

Strange behavior with tar

I am trying to create an archive using tar. I am specifying a list of directories using the -L option. For testing purposes I created a simple directory structure: /backup/test /backup/test/test1 /backup/test/test2 The file specified by the -L option, named files.txt, contains:... (8 Replies)
Discussion started by: judykstra
8 Replies

10. Shell Programming and Scripting

Strange behavior of grep

Hi All, I am facing a strange problem while grepping for a process. Here is the small script that i have written. It will look for any process running with the parameter passed to the script. If no process is running it should print appropriate message. $ cat t.ksh #!/bin/ksh set -x ... (9 Replies)
Discussion started by: veeresh_15
9 Replies
SED(1)							      General Commands Manual							    SED(1)

NAME
sed - stream editor SYNOPSIS
sed [ -n ] [ -g ] [ -e script ] [ -f sfile ] [ file ... ] DESCRIPTION
Sed copies the named files (standard input default) to the standard output, edited according to a script of commands. The -f option causes the script to be taken from file sfile; these options accumulate. If there is just one -e option and no -f's, the flag -e may be omitted. The -n option suppresses the default output; -g causes all substitutions to be global, as if suffixed g. A script consists of editing commands, one per line, of the following form: [address [, address] ] function [argument ...] In normal operation sed cyclically copies a line of input into a pattern space (unless there is something left after a command), applies in sequence all commands whose addresses select that pattern space, and at the end of the script copies the pattern space to the standard out- put (except under -n) and deletes the pattern space. An address is either a decimal number that counts input lines cumulatively across files, a that addresses the last line of input, or a con- text address, /regular-expression/, in the style of regexp(6), with the added convention that matches a newline embedded in the pattern space. A command line with no addresses selects every pattern space. A command line with one address selects each pattern space that matches 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 one line is selected.) Thereafter the process is repeated, looking again for the first address. Editing commands can be applied to non-selected pattern spaces by use of the negation function (below). An argument denoted text consists of one or more lines, all but the last of which end with to hide the newline. Backslashes in text are treated like backslashes in the replacement string of an command, and may be used to protect initial blanks and tabs against the stripping that is done on every script line. An argument denoted rfile or wfile must terminate the command line and must be preceded by exactly one blank. Each wfile is created before processing begins. There can be at most 120 distinct wfile arguments. a text Append. Place text on the output before reading the next input line. b label Branch to the : command bearing the label. If label is empty, branch to the end of the script. c text Change. Delete the pattern space. With 0 or 1 address or at the end of a 2-address range, place text on the output. Start the next cycle. d Delete the pattern space. Start the next cycle. D Delete the initial segment of the pattern space through the first newline. Start the next cycle. g Replace the contents of the pattern space by the contents of the hold space. G Append the contents of the hold space to the pattern space. h Replace the contents of the hold space by the contents of the pattern space. H Append the contents of the pattern space to the hold space. i text Insert. Place text on the standard output. n Copy the pattern space to the standard output. Replace the pattern space with the next line of input. N Append the next line of input to the pattern space with an embedded newline. (The current line number changes.) p Print. Copy the pattern space to the standard output. P Copy the initial segment of the pattern space through the first newline to the standard output. q Quit. Branch to the end of the script. Do not start a new cycle. r rfile Read the contents of rfile. Place them on the output before reading the next input line. s/regular-expression/replacement/flags Substitute the replacement string for instances of the regular-expression in the pattern space. Any character may be used instead of For a fuller description see regexp(6). Flags is zero or more of g Global. Substitute for all non-overlapping instances of the regular expression rather than just the first one. p Print the pattern space if a replacement was made. w wfile Write. Append the pattern space to wfile if a replacement was made. t label Test. Branch to the command bearing the label if any substitutions have been made since the most recent reading of an input line or execution of a If label is empty, branch to the end of the script. w wfile Write. Append the pattern space to wfile. x Exchange the contents of the pattern and hold spaces. y/string1/string2/ Transform. Replace all occurrences of characters in string1 with the corresponding character in string2. The lengths of string1 and string2 must be equal. !function Don't. Apply the function (or group, if function is only to lines not selected by the address(es). : label This command does nothing; it bears a label for b and t commands to branch to. = Place the current line number on the standard output as a line. { Execute the following commands through a matching only when the pattern space is selected. An empty command is ignored. EXAMPLES
sed 10q file Print the first 10 lines of the file. sed '/^$/d' Delete empty lines from standard input. sed 's/UNIX/& system/g' Replace every instance of by sed 's/ *$// drop trailing blanks /^$/d drop empty lines s/ */ replace blanks by newlines /g /^$/d' chapter* Print the files chapter1, chapter2, etc. one word to a line. nroff -ms manuscript | sed ' ${ /^$/p if last line of file is empty, print it } //N if current line is empty, append next line /^ $/D' if two lines are empty, delete the first Delete all but one of each group of empty lines from a formatted manuscript. SOURCE
/sys/src/cmd/sed.c SEE ALSO
ed(1), grep(1), awk(1), lex(1), sam(1), regexp(6) L. E. McMahon, `SED -- A Non-interactive Text Editor', Unix Research System Programmer's Manual, Volume 2. BUGS
If input is from a pipe, buffering may consume characters beyond a line on which a command is executed. SED(1)
All times are GMT -4. The time now is 04:31 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy