Sponsored Content
Top Forums Shell Programming and Scripting sed behaving oddly, repeats lines Post 302667847 by pereyrax on Saturday 7th of July 2012 02:43:22 PM
Old 07-07-2012
Alister, thanks! That's really helpful. I need to get my hands on a thorough sed manual
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Search for repeats in text file - how?

I have a text file that I want to search for repeated lines and print those lines. These would be lines in the file that appear more than once. Is there a way to do this? Thanks (4 Replies)
Discussion started by: aarondesk
4 Replies

2. Shell Programming and Scripting

sed and cut behaving differently

I have attached a file with few records. First 2 characters of each record are binary characters. I can remove it by and it works fine. But is behaving differently and removing more than expected characters. Can someone help me in accomplishing it through sed? Thanks in advance. (13 Replies)
Discussion started by: amicon007
13 Replies

3. UNIX for Dummies Questions & Answers

awk repeats counter

if I wanted to know if the word DOG(followed by several random numbers) appears in col 1, how many times will that same word DOG* appeared in col 2? This is a very large file Thanks! (7 Replies)
Discussion started by: verse123
7 Replies

4. UNIX for Dummies Questions & Answers

Can't figure out why this repeats

#!/bin/sh while IFS=: read address port; do : ${port:=443} address=$address port=$port cd $f_location number=`grep "$address" thing.txt -A 1 | grep "addresses=" | cut -d'"' -f2` echo "$address,$port,$number,$answer" >>... (9 Replies)
Discussion started by: shade917
9 Replies

5. Shell Programming and Scripting

Remove brackets repeats and separate in columns

Hi all, I want to remove the remove bracket sign ( ) and put in the separate column I also want to remove the repeated entry like in first row in below input (PA156) is repeated ESR1 (PA156) leflunomide (PA450192) (PA156) leflunomide (PA450192) CHST3 (PA26503) docetaxel... (4 Replies)
Discussion started by: manigrover
4 Replies

6. Solaris

Remove oddly named file

I accidentally saved a txt file in vi with the name ":q!". no amount of regex tomfoolery I can think of will allow me to remove the file. anyone got any ideas? (4 Replies)
Discussion started by: os2mac
4 Replies

7. Shell Programming and Scripting

sed parser behaving strange on replacing multiple words in multiple files

I have 4000 files like $cat clus_grp_seq10_g.phy 18 1002 anig_OJJ65951_1 ATGGTTTCGCAGCGTGATAGAGAATTGTTTAGGGATGATATTCGCTCGCGAGGAACGAAGCTCAATGCTGCCGAGCGCGAGAGTCTGCTAAGGCCATATCTGCCAGATCCGTCTGACCTTCCACGCAGGCCACTTCAGCGGCGCAAGAAGGTTCCTCG aver_OOF92921_1 ... (1 Reply)
Discussion started by: sammy777888
1 Replies

8. UNIX for Beginners Questions & Answers

Non printing option in sed is behaving oddly

Hi I'm having a problem with a sed command that I thought I was using correctly but apparently that's not the case. I was hoping someone here could point out what it is I am doing wrong? I am using the print, no print option for a matched pattern in sed. Everything seemed to be working fine... (5 Replies)
Discussion started by: Paul Walker
5 Replies

9. UNIX for Beginners Questions & Answers

Non printing option in sed is behaving oddly

Hi I'm having a problem with a sed command that I thought I was using correctly but apparently that's not the case. I was hoping someone here could point out what it is I am doing wrong? I am using the print, no print option for a matched pattern in sed. Everything seemed to be working fine... (2 Replies)
Discussion started by: harveyclayton
2 Replies
divert(3)							     EN Tools								 divert(3)

NAME
Divert - Text Diversion Filter SYNOPSIS
divert [-o outputfile] [-q] [-v] [inputfile] DESCRIPTION
The divert program reads inputfile or from "stdin" and applies a 2-pass diversion filter to its contents. In pass 1 all diversion locations are accumulated and in pass 2 these locations are recursively expanded at their dump positions. The diversion filter is controlled by directives found in the input data: {#NAME#} (or <<NAME>>) This defines the dump position of the location NAME. All accumulated data which finally has to been diverted to NAME is inserted at this data position. Notice: the final data of a location NAME has not to be known at this point, because the expansion of such location dumps are done in pass 2. You can also dump a location more than once, but the contents is always the same, independent of the data position where the location dump tag stays. The NAME can be any symbolic name matching "[a-zA-Z][a-zA-Z0-9_]*". {#[!]NAME[!]#: (or ..[!]NAME[!]>>) This enters the location NAME (or diverts the data flow to it, hence the name for this filter). In other words: the data flow now goes on at location NAME. All following data (up to end of file or the next location leave tag) gets appended to location NAME. You can nest diversions by entering other locations at any point, because the locations are remembered on a stack. The default entered location is named ``"main"''. The top most location is named ``"null"'' which neither can be entered nor leaved explicitly. But of course the ``"null"'' diversion can be manually dumped, for instance when using it for error messages. There are two special features for diverting data which are controlled by the ""!"" characters preceding or following the NAME identifier: !NAME This sets the data flow position to the begin of location NAME, i.e. it actually discards the current (already diverted) contents of location NAME before entering it. Use this to overwrite a locations contents. NAME! This marks this location entry as overwritable, i.e. it enters location NAME but when the corresponding leave tag is found, the data-flow position for NAME gets automatically reset to its begin. Use this if you want to set the default contents for a location which only gets used if no other diversions occur to it (because any following diversions to this location will be overwrite the contents). This feature is usually used for a template scheme. !NAME! Just the combination of the above two features. Use this to both discard the current contents of location NAME and set a new default for it. :#[NAME]#} (or <<[NAME]..) This leaves the current location, i.e. enters again the location which was active when this location was entered. There is no need to leave all locations at the end of the input data. All still entered locations are automatically left at end of file because this is essential for a template scheme. Notice that there are two ways of using (and thinking) about the filtering mechanism this program provides: Macro Mechanism This is the "predefined" way of thinking here. Use it like this: FOO {#BAR#} QUUX {#BAR#: BAZ :##} Here you are thinking of the mechanism as a macro mechanism where you expand a macro at one data position while you define it via begin and end tags. Diversion Mechanism This is the alternative way of thinking. Use it like this: FOO <<BAR>> QUUX ..BAR>> BAZ <<.. In other words: You are thinking of the mechanism as a diversion mechanism where you dump a location at one data position while you divert to it by entering end leaving the location (here BAR) at other positions. You can even intermix both ways because both are just alternative syntax variants which are treated the same. EXAMPLE
{#HEAD#} {#BODY#} {#FOOT#} {#FOOT#: Quux :##} {#BODY#: Bar :##} {#HEAD#: Foo :##} OPTIONS
-o outputfile This redirects the output to outputfile. Usually the output will be send to stdout if no such option is specified or outputfile is ``"-"''. -q This sets quiet mode where warnings are suppressed. -v This sets verbose mode where some processing information will be given on stderr. AUTHORS
Ralf S. Engelschall rse@engelschall.com www.engelschall.com Denis Barbier barbier@engelschall.com EN Tools 2014-04-16 divert(3)
All times are GMT -4. The time now is 09:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy