05-17-2007
Shell, I like it, very simple, I don't think it addresses the issue of my new file containing everything except the first line though, does it? How can I get the newfile to exclude the first line from the source file, is that the cut command again?
Thx again
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
What is the easiest way to delete a line from a file?
I have a file that contains list for Domestic and Foreign customers.
I want to delete all lines staring with Foreing.
TIA (4 Replies)
Discussion started by: elchalateco
4 Replies
2. Shell Programming and Scripting
Hi all,
I would like to delete a line in file.txt which has a list of filename.
example:
file_a
file_b
file_c
lets say i have file_b in my directory, then i should delete file_b in file.txt and get output file.txt with only file_a and file_b.
Below is my script, my result is still ... (12 Replies)
Discussion started by: dta4316
12 Replies
3. UNIX for Dummies Questions & Answers
Hi ,
I have a file it content is like that
/vol.nas/u08/aip_triage/hany/Tesko/:CC::RPAS
/home/biblawh/myscript:CC::RPAS
i need to search for a certain pattern inside that file and delete the line if i find this pattern without redirecting the output into another file .
so i used the... (0 Replies)
Discussion started by: ramezernest
0 Replies
4. Shell Programming and Scripting
Hi,
I have a file which contains entries with different numbers, for example:
275|24hroff|sel,fill,dbw|
2758|24hroff|sel,fill,dbw|
2765|24hroff|sel,fill,dbw|
2920|24hroff|sel,fill,dbw|
I need to delete a line which contains certian number, for instance 275
I was trying to use 'sed' but... (3 Replies)
Discussion started by: aoussenko
3 Replies
5. UNIX for Dummies Questions & Answers
Hi,
Need to delete a line from a file, file is too large so cannot use vi.
I know the line number that has to be deleted...
How can this be done ? (8 Replies)
Discussion started by: rohini
8 Replies
6. Shell Programming and Scripting
hi all,
i have trackfile.txt which contains the data as
0 /home8/mc09ats/UnixCw/t1
1 /home8/mc09ats/UnixCw/t2
2 /home8/mc09ats/UnixCw/t3
3 /home8/mc09ats/UnixCw/t4
if user says delete 1 then i want to delete 1 /home8/mc09ats/UnixCw/t2
line from... (3 Replies)
Discussion started by: AbhijitIT
3 Replies
7. Shell Programming and Scripting
I have a file of following form
2886758410 2886758500 17 1999-Mar-18 16:26:26 1 0 52 139 1129
2886758420 2886758500 17 1999-Mar-18 16:26:35 1 0 52 139 1131
2886758420 2886758500 17 1999-Mar-18 16:26:41 0 0 56 56 1132... (4 Replies)
Discussion started by: vaibhavkorde
4 Replies
8. Shell Programming and Scripting
Hi gurus,
I have one file it may contains one line is "START" or "FINISH" either one of them.
I use below command to delete it, but it doens't work.
sed '/^START\|^END/d' <inputfile > outfile
anybody can help me to fix this.
thanks in advance. (12 Replies)
Discussion started by: ken6503
12 Replies
9. UNIX for Advanced & Expert Users
Hi ,
i have a file with data as below.This is same file. But actual file contains to many rows.
i want to search for a string "Field 039 00" and delete that line and previous 3 lines in that file.. Can some body suggested me how can i do using either sed or awk command ?
Field 004... (7 Replies)
Discussion started by: vadlamudy
7 Replies
10. UNIX for Beginners Questions & Answers
Hi, I want to do file1 to file2. Rows will be different every time. Thanks.
file1
Fru-Name :BCNMB-B Fru-Location :/chassis-1/motherboard-1 Node-Name :LMP-1-1-1
Fru-Name :BMPP2-B Fru-Location :/chassis-1/slot-1 Node-Name :CFPU-0
Fru-Name :BMPP2-B Fru-Location... (2 Replies)
Discussion started by: ozcanaydin
2 Replies
LEARN ABOUT XFREE86
git-check-ignore
GIT-CHECK-IGNORE(1) Git Manual GIT-CHECK-IGNORE(1)
NAME
git-check-ignore - Debug gitignore / exclude files
SYNOPSIS
git check-ignore [options] pathname...
git check-ignore [options] --stdin
DESCRIPTION
For each pathname given via the command-line or from a file via --stdin, check whether the file is excluded by .gitignore (or other input
files to the exclude mechanism) and output the path if it is excluded.
By default, tracked files are not shown at all since they are not subject to exclude rules; but see '--no-index'.
OPTIONS
-q, --quiet
Don't output anything, just set exit status. This is only valid with a single pathname.
-v, --verbose
Also output details about the matching pattern (if any) for each given pathname. For precedence rules within and between exclude
sources, see gitignore(5).
--stdin
Read pathnames from the standard input, one per line, instead of from the command-line.
-z
The output format is modified to be machine-parseable (see below). If --stdin is also given, input paths are separated with a NUL
character instead of a linefeed character.
-n, --non-matching
Show given paths which don't match any pattern. This only makes sense when --verbose is enabled, otherwise it would not be possible to
distinguish between paths which match a pattern and those which don't.
--no-index
Don't look in the index when undertaking the checks. This can be used to debug why a path became tracked by e.g. git add . and was
not ignored by the rules as expected by the user or when developing patterns including negation to match a path previously added with
git add -f.
OUTPUT
By default, any of the given pathnames which match an ignore pattern will be output, one per line. If no pattern matches a given path,
nothing will be output for that path; this means that path will not be ignored.
If --verbose is specified, the output is a series of lines of the form:
<source> <COLON> <linenum> <COLON> <pattern> <HT> <pathname>
<pathname> is the path of a file being queried, <pattern> is the matching pattern, <source> is the pattern's source file, and <linenum> is
the line number of the pattern within that source. If the pattern contained a ! prefix or / suffix, it will be preserved in the output.
<source> will be an absolute path when referring to the file configured by core.excludesFile, or relative to the repository root when
referring to .git/info/exclude or a per-directory exclude file.
If -z is specified, the pathnames in the output are delimited by the null character; if --verbose is also specified then null characters
are also used instead of colons and hard tabs:
<source> <NULL> <linenum> <NULL> <pattern> <NULL> <pathname> <NULL>
If -n or --non-matching are specified, non-matching pathnames will also be output, in which case all fields in each output record except
for <pathname> will be empty. This can be useful when running non-interactively, so that files can be incrementally streamed to STDIN of a
long-running check-ignore process, and for each of these files, STDOUT will indicate whether that file matched a pattern or not. (Without
this option, it would be impossible to tell whether the absence of output for a given file meant that it didn't match any pattern, or that
the output hadn't been generated yet.)
Buffering happens as documented under the GIT_FLUSH option in git(1). The caller is responsible for avoiding deadlocks caused by
overfilling an input buffer or reading from an empty output buffer.
EXIT STATUS
0
One or more of the provided paths is ignored.
1
None of the provided paths are ignored.
128
A fatal error was encountered.
SEE ALSO
gitignore(5) git-config(1) git-ls-files(1)
GIT
Part of the git(1) suite
Git 2.17.1 10/05/2018 GIT-CHECK-IGNORE(1)