Hi,
Please let me know how to find text and print text and its previous line. Please don't get irritated few days back I asked text and next line. I am using HP-UX 11.11
Thanks for your help. (6 Replies)
This is my first post, please be nice. I have tried to google and read different tutorials.
The task at hand is:
Input file input.txt (example)
abc123defhij-E-1234jslo
456ujs-W-abXjklp
From this file the task is to grep the -E- and -W- strings that are unique and write a new file... (5 Replies)
i have nasty html file with 2000+ simbols in 1 row...i need to remove whole the code except title="Some title..." and store those into file with titles (the whole text is in variable text)
i've tried something like this:
echo $text | sed 's/.*\(title=\".+\"\).*/\1/' > titles.html
BUT it does... (13 Replies)
Hello all,
I have one input file like this:
List 1
mail a
mail b
mail c
List 2
mail d
mail e
mail f
mail g
List 3
mail h
mail i
And I want something like that by using linux:
List 1,mail a,mail b,mail c (4 Replies)
I have a text file with a list of items/patterns:
ConsensusfromCGX_alldays_trimmedcollapsedfilteredreadscontiglist(229095contigs)contig12238
ConsensusfromCGX_alldays_trimmedcollapsedfilteredreadscontiglist(229095contigs)contig34624... (1 Reply)
Hej all,
I have a LS-DYNA keyword file which I want to extract the node coordinates from it to another file for processing and then returning the result coordinates to the same place, the structure of the file is like:
Keyword file:
5010497 -266.6623535 -446.2596130 ... (3 Replies)
Currently, I have a print filter that takes a text file, that convert it into PCL which then gets to a HP printer. This works.
Now I need to embedded a image file within the text file.
I'm able to convert the image file into PCL and I can cat both files together to into a single document... (1 Reply)
I'm trying to pull an image source url from a html source file. I'm new with regex. I'm in BaSH. I've tried grep -E 'http.*jpg' file which highlights the text, but gives me 2 problems:
1) Results aren't stand alone and can't be piped to another command. (I believe it includes everything in... (5 Replies)
Hi all,
I got a txt here and I need to extract all D 8888 44 and D 8888 43 + next field
=",g("en")];f._sn&&(f._sn= "og."+f._sn);for(var n in f)l.push("&"),l.push(g(n)),l.push("="),l.push(g(f));l.push("&emsg=");l.push(g(d.name+":"+d.message));var m=l.join("");Ea(m)&&(m=m.substr(0,2E3));c=m;var... (5 Replies)
hi all,
trying this using shell/bash with sed/awk/grep
I have two files, one containing one column, the other containing multiple columns (comma delimited).
file1.txt
abc12345
def12345
ghi54321
...
file2.txt
abc1,text1,texta
abc,text2,textb
def123,text3,textc
gh,text4,textd... (6 Replies)
Discussion started by: shogun1970
6 Replies
LEARN ABOUT DEBIAN
git-annotate
GIT-ANNOTATE(1) Git Manual GIT-ANNOTATE(1)NAME
git-annotate - Annotate file lines with commit information
SYNOPSIS
git annotate [options] file [revision]
DESCRIPTION
Annotates each line in the given file with information from the commit which introduced the line. Optionally annotates from a given
revision.
The only difference between this command and git-blame(1) is that they use slightly different output formats, and this command exists only
for backward compatibility to support existing scripts, and provide a more familiar command name for people coming from other SCM systems.
OPTIONS -b
Show blank SHA-1 for boundary commits. This can also be controlled via the blame.blankboundary config option.
--root
Do not treat root commits as boundaries. This can also be controlled via the blame.showroot config option.
--show-stats
Include additional statistics at the end of blame output.
-L <start>,<end>
Annotate only the given line range. <start> and <end> can take one of these forms:
o number
If <start> or <end> is a number, it specifies an absolute line number (lines count from 1).
o /regex/
This form will use the first line matching the given POSIX regex. If <end> is a regex, it will search starting at the line given by
<start>.
o +offset or -offset
This is only valid for <end> and will specify a number of lines before or after the line given by <start>.
-l
Show long rev (Default: off).
-t
Show raw timestamp (Default: off).
-S <revs-file>
Use revisions from revs-file instead of calling git-rev-list(1).
--reverse
Walk history forward instead of backward. Instead of showing the revision in which a line appeared, this shows the last revision in
which a line has existed. This requires a range of revision like START..END where the path to blame exists in START.
-p, --porcelain
Show in a format designed for machine consumption.
--line-porcelain
Show the porcelain format, but output commit information for each line, not just the first time a commit is referenced. Implies
--porcelain.
--incremental
Show the result incrementally in a format designed for machine consumption.
--encoding=<encoding>
Specifies the encoding used to output author names and commit summaries. Setting it to none makes blame output unconverted data. For
more information see the discussion about encoding in the git-log(1) manual page.
--contents <file>
When <rev> is not specified, the command annotates the changes starting backwards from the working tree copy. This flag makes the
command pretend as if the working tree copy has the contents of the named file (specify - to make the command read from the standard
input).
--date <format>
The value is one of the following alternatives: {relative,local,default,iso,rfc,short}. If --date is not provided, the value of the
blame.date config variable is used. If the blame.date config variable is also not set, the iso format is used. For more information,
See the discussion of the --date option at git-log(1).
-M|<num>|
Detect moved or copied lines within a file. When a commit moves or copies a block of lines (e.g. the original file has A and then B,
and the commit changes it to B and then A), the traditional blame algorithm notices only half of the movement and typically blames the
lines that were moved up (i.e. B) to the parent and assigns blame to the lines that were moved down (i.e. A) to the child commit. With
this option, both groups of lines are blamed on the parent by running extra passes of inspection.
<num> is optional but it is the lower bound on the number of alphanumeric characters that git must detect as moving/copying within a
file for it to associate those lines with the parent commit. The default value is 20.
-C|<num>|
In addition to -M, detect lines moved or copied from other files that were modified in the same commit. This is useful when you
reorganize your program and move code around across files. When this option is given twice, the command additionally looks for copies
from other files in the commit that creates the file. When this option is given three times, the command additionally looks for copies
from other files in any commit.
<num> is optional but it is the lower bound on the number of alphanumeric characters that git must detect as moving/copying between
files for it to associate those lines with the parent commit. And the default value is 40. If there are more than one -C options given,
the <num> argument of the last -C will take effect.
-h
Show help message.
SEE ALSO git-blame(1)GIT
Part of the git(1) suite
Git 1.7.10.4 11/24/2012 GIT-ANNOTATE(1)