Assuming the tags are in order as shown in your sample, the following should work:
Note, however, that your code (and this trivial modification of it) are not just matching tag names, they are matching tag names and text that is not part of the tag name (in the case of ref2, it is only matching text since the tag name is re2 instead of ref2).
Of course, you could also use:
or:
Last edited by Don Cragun; 03-24-2016 at 10:00 PM..
Reason: Add grep/paste alternative
This User Gave Thanks to Don Cragun For This Post:
suppose i have one file
file A
18
24
30
35
38
45
55
Another file file B
08_46 A 16 V -0.36 0.23 E : 1.41
08_46 A 17 D -1.04 0.22 E : 0.84
08_46 A 18 Q -0.49 0.12 E : 0.06
08_46 A 19 G 0.50 0.14 E : 0.05
08_46 A 20 V ... (5 Replies)
Hello,
Can anybody help me to correct my sed syntax to find the string and print previous two lines and current line and next one line.
i am using string as "testing"
netstat -v | sed -n -e '/test/{x;2!p;g;$!N;p;D;}' -e h
i am able to get the previous line current line next line but... (1 Reply)
Hello.
I've been banging my head against walls trying to search a comma delimited file, using awk. I'm trying to search a "column" for a specific parameter, if it matches, then I'd like to print the whole line.
I've read in multiple texts:
awk -F, '{ if ($4 == "string") print $0 }'... (2 Replies)
I have multiple config files where I need to pull the ip address from loopback3. The format is the same in every file, the ip is the second line after interface loopback3.
interface loopback2 loopback
description router ID
ip address 192.168.1.1
interface loopback3 loopback
description... (3 Replies)
All I want is to look for the pattern in the file...If I found it at # places... I want print lines after those pattern(line) until I find a blank line.
Log EXAMPLE :
MT:Exception caught
The following Numbers were affected:
1234
2345
2346
Error
java.lang.InternalError:... (3 Replies)
I have a text file ( basically a log file) and i have 2 words (alpha, beta),
Now i want to search these two words in one line and then print next 15 lines in a temp file. there would be many lines with alpha and beta But I need only last occurrence with "alpha" and "beta" and next 15 lines.
... (4 Replies)
if the first string matches then print the previous line and current line and also print the following lines if the other string search matches.
Input
------
TranTime 2012 10 12
The Record starts here
Accountnumber: 4632473431274
TxnCode 323
TranID 329473242834
ccsdkcnsdncskd... (7 Replies)
Hi,
I am using the following code to fetch lines that are generated in last 1 hr . Hence, I am using date function to calculate -last 1 hr & the current hr and then somehow use awk (or sed-if someone could guide me better)
with some regex pattern.
dt_1=`date +%h" "%d", "%Y\ %l -d "1 hour... (10 Replies)
Dear all
I want to search special string in file and then print next all line in one line until blank lines come. Help me plz for same. My input file and desire op file is as under.
i/p file:
A1/EXT "BSCABD1_21233G1" 757 130823 1157
RADIO X-CEIVER ADMINISTRATION
BTS EXTERNAL FAULT
... (7 Replies)
GOODNUMBERS="1 2 3 4 5 6 3 3 34 34 5 66 12"
BADNUMBERS="7 3 12 5 66"
for eachnum in `echo ${GOODNUMBERS}`
do
echo ${BADNUMBERS} | gawk -v threshold=${eachnum} '$1 != threshold'
done
what im trying to do with the above is, i want to print numbers that are in the GOODNUMBERS... (10 Replies)
Discussion started by: SkySmart
10 Replies
LEARN ABOUT LINUX
git-check-ref-format
GIT-CHECK-REF-FOR(1) Git Manual GIT-CHECK-REF-FOR(1)NAME
git-check-ref-format - Ensures that a reference name is well formed
SYNOPSIS
git check-ref-format [--normalize]
[--[no-]allow-onelevel] [--refspec-pattern]
<refname>
git check-ref-format --branch <branchname-shorthand>
DESCRIPTION
Checks if a given refname is acceptable, and exits with a non-zero status if it is not.
A reference is used in Git to specify branches and tags. A branch head is stored in the refs/heads hierarchy, while a tag is stored in the
refs/tags hierarchy of the ref namespace (typically in $GIT_DIR/refs/heads and $GIT_DIR/refs/tags directories or, as entries in file
$GIT_DIR/packed-refs if refs are packed by git gc).
Git imposes the following rules on how references are named:
1. They can include slash / for hierarchical (directory) grouping, but no slash-separated component can begin with a dot . or end with
the sequence .lock.
2. They must contain at least one /. This enforces the presence of a category like heads/, tags/ etc. but the actual names are not
restricted. If the --allow-onelevel option is used, this rule is waived.
3. They cannot have two consecutive dots .. anywhere.
4. They cannot have ASCII control characters (i.e. bytes whose values are lower than 40, or 177 DEL), space, tilde ~, caret ^, or colon
: anywhere.
5. They cannot have question-mark ?, asterisk *, or open bracket [ anywhere. See the --refspec-pattern option below for an exception to
this rule.
6. They cannot begin or end with a slash / or contain multiple consecutive slashes (see the --normalize option below for an exception to
this rule)
7. They cannot end with a dot ..
8. They cannot contain a sequence @{.
9. They cannot be the single character @.
10. They cannot contain a .
These rules make it easy for shell script based tools to parse reference names, pathname expansion by the shell when a reference name is
used unquoted (by mistake), and also avoids ambiguities in certain reference name expressions (see gitrevisions(7)):
1. A double-dot .. is often used as in ref1..ref2, and in some contexts this notation means ^ref1 ref2 (i.e. not in ref1 and in ref2).
2. A tilde ~ and caret ^ are used to introduce the postfix nth parent and peel onion operation.
3. A colon : is used as in srcref:dstref to mean "use srcref's value and store it in dstref" in fetch and push operations. It may also be
used to select a specific object such as with git cat-file: "git cat-file blob v1.3.3:refs.c".
4. at-open-brace @{ is used as a notation to access a reflog entry.
With the --branch option, it expands the "previous branch syntax" @{-n}. For example, @{-1} is a way to refer the last branch you were on.
This option should be used by porcelains to accept this syntax anywhere a branch name is expected, so they can act as if you typed the
branch name.
OPTIONS
--[no-]allow-onelevel
Controls whether one-level refnames are accepted (i.e., refnames that do not contain multiple /-separated components). The default is
--no-allow-onelevel.
--refspec-pattern
Interpret <refname> as a reference name pattern for a refspec (as used with remote repositories). If this option is enabled, <refname>
is allowed to contain a single * in place of a one full pathname component (e.g., foo/*/bar but not foo/bar*).
--normalize
Normalize refname by removing any leading slash (/) characters and collapsing runs of adjacent slashes between name components into a
single slash. Iff the normalized refname is valid then print it to standard output and exit with a status of 0. (--print is a
deprecated way to spell --normalize.)
EXAMPLES
o Print the name of the previous branch:
$ git check-ref-format --branch @{-1}
o Determine the reference name to use for a new branch:
$ ref=$(git check-ref-format --normalize "refs/heads/$newbranch") ||
die "we do not like '$newbranch' as a branch name."
GIT
Part of the git(1) suite
Git 1.8.5.3 01/14/2014 GIT-CHECK-REF-FOR(1)