Sponsored Content
Full Discussion: Sed command with \1
Top Forums UNIX for Dummies Questions & Answers Sed command with \1 Post 302719779 by Don Cragun on Tuesday 23rd of October 2012 06:00:44 AM
Old 10-23-2012
In case bipinajith's answer doesn't give you enough information to figure out what is going on, maybe the following will help. The "remembered pattern" mentioned by bipinajith is known in the standards as a subexpression. In a basic regular expression (BRE), which is the type of RE used in sed's s[ubstitute] command, a subexpression is of the form\(BRE\)and matches whatever the BRE matches without the\(and\).

The string matched by a subexpression can be referenced by a back-reference expression. A back-reference expression is of the form \n where n is a single decimal digit 1 through 9. When there are multiple subexpressions, they are numbered by counting the occurrences of\(from left to right.

The following example may help. Running this script:
Code:
#!/bin/ksh
sed 'p;s/[^a-zA-Z0-9]*\([a-zA-Z]*\)\([0-9]\([0-9]\)\([0-9]\)\([0-9]\)\)/*1st=\1,2nd=\2,3rd=\3,4th=\4,5th=\5*/' <<EOF
abc1234
234bcd56789
.AbC123.XYZ01234.
EOF

produces the output:
Code:
abc1234
*1st=abc,2nd=1234,3rd=2,4th=3,5th=4*
234bcd56789
234*1st=bcd,2nd=5678,3rd=6,4th=7,5th=8*9
.AbC123.XYZ01234.
.AbC123*1st=XYZ,2nd=0123,3rd=1,4th=2,5th=3*4.

These 3 Users Gave Thanks to Don Cragun For This Post:
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

awk/sed Command : Parse parameter file / send the lines to the ksh export command

Sorry for the duplicate thread this one is similar to the one in https://www.unix.com/shell-programming-scripting/88132-awk-sed-script-read-values-parameter-files.html#post302255121 Since there were no responses on the parent thread since it got resolved partially i thought to open the new... (4 Replies)
Discussion started by: rajan_san
4 Replies

2. Shell Programming and Scripting

Loop with sed command to replace line with sed command in it

Okay, title is kind of confusion, but basically, I have a lot of scripts on a server that I need to replace a ps command, however, the new ps command I'm trying to replace the current one with pipes to sed at one point. So now I am attempting to create another script that replaces that line. ... (1 Reply)
Discussion started by: cbo0485
1 Replies

3. UNIX for Dummies Questions & Answers

some help with the sed command please

hi all, attached you can find a small txt file ( .txt ), GIVEN that past_scheduler="islip" and scheduler="mucf" can somebody please tell me WHY sed 's/-u '$past_scheduler'/-u '$scheduler'/g' .txt > .txt.temp fails ? thanx (3 Replies)
Discussion started by: OneDreamCloser
3 Replies

4. Shell Programming and Scripting

Convert Sed command to perl command

Hello, Can any perl experts help me convert my sed string to perl. I am unsuccessful with this. I have to remove this string from html files OAS_AD('Top'); I have come up with this. However the requirement is in perl. for find in $(find . -type f -name "file1.html") ; do cat $find |... (2 Replies)
Discussion started by: abacus
2 Replies

5. UNIX for Dummies Questions & Answers

sed insert command and variable expansion/command substitution

I know this script is crummy, but I was just messing around.. how do I get sed's insert command to allow variable expansion to show the filename? #!/bin/bash filename=`echo $0` /usr/bin/sed '/#include/ { i\ the filename is `$filename` }' $1 exit 0 (8 Replies)
Discussion started by: glev2005
8 Replies

6. UNIX for Advanced & Expert Users

sed command

Hi..... I'm using sed command for replace the words in a file cat >test.txt My test.txt contains Mary had a little ham Mary fried a lot of spam Jack ate a Spam sandwich Jill had a lamb spamwich Marry had a spicy wich $ sed 's/wich$/mirchi/g' test.txt output is: Mary had a little ham... (24 Replies)
Discussion started by: ksrivani
24 Replies

7. Shell Programming and Scripting

sed returns error "sed: -e expression #1, char 18: unterminated `s' command"

Hello All, I have something like below LDC100/rel/prod/libinactrl.a LAA2000/rel/prod/libinactrl.a I want to remove till first forward slash that is outputshould be as below rel/prod/libinactrl.a rel/prod/libinactrl.a How can I do that ??? (8 Replies)
Discussion started by: anand.shah
8 Replies

8. Shell Programming and Scripting

sed Command

Hello, I'm working with this command which I'm having trouble understanding it: sed -e '1,$ s/SUB/N/g' < $1 > file.txt Where SUB stand for an special character with code in ASCII is 0x1A, notepad read it as a right arrow. Any help will be appreciated. (5 Replies)
Discussion started by: emilioveras
5 Replies

9. Shell Programming and Scripting

sed and awk giving error ./sample.sh: line 13: sed: command not found

Hi, I am running a script sample.sh in bash environment .In the script i am using sed and awk commands which when executed individually from terminal they are getting executed normally but when i give these sed and awk commands in the script it is giving the below errors :- ./sample.sh: line... (12 Replies)
Discussion started by: satishmallidi
12 Replies

10. UNIX for Dummies Questions & Answers

Output of sed command to another sed command

Hi All, I'm relatively new to Unix scripting and am trying to get my head around piping. I'm trying to take a header record from one file and prepend it to another file. I've done this by creating several temp files but i'm wondering if there is a cleaner way to do this. I'm thinking... (10 Replies)
Discussion started by: BigCroyd
10 Replies
GROG(1) 						      General Commands Manual							   GROG(1)

NAME
grog -- guess options for a following groff command SYNOPSIS
grog [-C] [--run] [--warnings] [--ligatures] [ groff-option ....] [--] [ filespec ....] grog -h | --help grog -v | --version DESCRIPTION
grog reads the input (file names or standard input) and guesses which of the groff(1) options are needed to perform the input with the groff program. The corresponding groff command is usually displayed in standard output. With the option --run, the generated line is output into standard error and the generated groff command is run on the standard output. OPTIONS
The option -v or --version prints information on the version number. Also -h or --help prints usage information. Both of these options automatically end the grog program. Other options are thenignored, and no groff command line is generated. The following 3 options are the only grog options, -C this option means enabling the groff compatibility mode, which is also transfered to the generated groff command line. --ligatures this option forces to include the arguments -P-y -PU within the generated groff command line. --run with this option, the command line is output at standard error and then run on the computer. --warnings with this option, some more warnings are output to standard error. All other specified short options (words starting with one minus character -) are interpreted as groff options or option clusters with or without argument. No space is allowed between options and their argument. Except from the -marg options, all options will be passed on, i.e. they are included unchanged in the command for the output without effecting the work of grog. A filespec argument can either be the name of an existing file or a single minus - to mean standard input. If no filespec is specified standard input is read automatically. DETAILS
grog reads all filespec parameters as a whole. It tries to guess which of the following groff options are required for running the input under groff: -e, -g, -G, -j, -J, -p, -R, -s, -t. -man, -mdoc, -mdoc-old, -me, -mm, -mom, and -ms. The guessed groff command including those options and the found filespec parameters is put on the standard output. It is possible to specify arbitrary groff options on the command line. These are passed on the output without change, except for the -marg options. The groff program has trouble when the wrong -marg option or several of these options are specified. In these cases, grog will print an error message and exit with an error code. It is better to specify no -marg option. Because such an option is only accepted and passed when grog does not find any of these options or the same option is found. If several different -marg options are found by grog an error message is produced and the program is terminated with an error code. But the output is written with the wrong options nevertheless. Remember that it is not necessary to determine a macro package. A roff file can also be written in the groff language without any macro package. grog will produce an output without an -marg option. As groff also works with pure text files without any roff requests, grog cannot be used to identify a file to be a roff file. The groffer(1) program heavily depends on a working grog. The grog source contains two files written in different programming languages: grog.pl is the Perl version, while grog.sh is a shell script using awk(1). During the run of make(1), it is determined whether the system contains a suitable version of perl(1). If so, grog.pl is transformed into grog; otherwise grog.sh is used instead. EXAMPLES
* Calling grog meintro.me results in groff -me meintro.me So grog recognized that the file meintro.me is written with the -me macro package. * On the other hand, grog pic.ms outputs groff -p -t -e -ms pic.ms Besides determining the macro package -ms, grog recognized that the file pic.ms additionally needs -pte, the combination of -p for pic, -t for tbl, and -e for eqn. * If both of the former example files are combined by the command grog meintro.me pic.ms an error message is sent to standard error because groff cannot work with two different macro packages: grog: error: there are several macro packages: -me -ms Additionally the corresponding output with the wrong options is printed to standard output: groff -pte -me -ms meintro.me pic.ms But the program is terminated with an error code. * The call of grog -ksS -Tdvi grnexmpl.g contains several groff options that are just passed on the output without any interface to grog. These are the option cluster -ksS con- sisting of -k, -s, and -S; and the option -T with argument dvi. The output is groff -k -s -S -Tdvi grnexmpl.g so no additional option was added by grog. As no option -marg was found by grog this file does not use a macro package. SEE ALSO
groff(1), groffer(1) troff(1), tbl(1), pic(1), chem(1), eqn(1), refer(1), grn(1), grap(1), soelim(1) Man-pages of section 1 can be viewed with either $ man name for text mode or $ groffer name for graphical mode (default is PDF mode). groff_me(7), groff_ms(7), groff_mm(7), groff_mom(7), groff_man(7) Man-pages of section 7 can be viewed with either with $ man 7 name for text mode or $ groffer 7 name for graphical mode (default is PDF mode). COPYING
Copyright (C) 1989-2014 Free Software Foundation, Inc. This file is part of grog, which is part of groff, a free software project. You can redistribute it and/or modify it under the terms of the GNU General Public License version 2 (GPL2) as published by the Free Software Foundation. groff is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. The text for GPL2 is available in the internet at GNU copyleft site <http://www.gnu.org/licenses/gpl-2.0.txt>. AUTHORS
Written by James Clark. Maintained by Werner Lemberg <wl@gnu.org>. Rewritten and put under GPL by Bernd Warken <groff-bernd.warken-72@web.de>. Groff Version 1.22.3 10 February 2018 GROG(1)
All times are GMT -4. The time now is 11:12 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy