10-23-2017
The grep -l "Calling appalert" gives the pathnames of the files that have a line with Calling appalert.
Do you want something else?
Then give an example: a sample of an input file with a matching and a non-matching line, and the expected output.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Dear all,
I am reading a file that has 1 column. While reading I must find the line references from the another file. The following shell doesn't works.
Please help
#!/bin/bash
while read filename; do
grep ${filename} fs_full.dat >> unprocfull.dat;
done < unproc.dat
But when... (2 Replies)
Discussion started by: mr_bold
2 Replies
2. Shell Programming and Scripting
Hello! I think this should be an easy solution. I have a large file with many fields of data. The first field has a unique identifier (a subject number) for every record for a chunk of data. Something like this:
There were ten experimental conditions (ec), but the ec is identified by only... (11 Replies)
Discussion started by: ccox85
11 Replies
3. Shell Programming and Scripting
I have inherited the UNIX scripting duties for our team and have only been at this for a few months so I apologize for what may be a simple question.
We have a script we are reworking. Part of this script takes a parameter and reads a csv file. When it finds a matching line, the cut command is... (4 Replies)
Discussion started by: 15a0
4 Replies
4. UNIX for Advanced & Expert Users
Hi all,
I would like to ask whether in Unix shell/perl have any functions or command to allow grep/cat/read a file inside compressed .tgz without extract it?
I know we can tar tvf a compressed tgz but this only allow we read the path/filename contained inside the tarball. If we want to read... (3 Replies)
Discussion started by: mayshy
3 Replies
5. UNIX for Dummies Questions & Answers
I have two files
file1.txt
angie
mary
susan
file2.txt
angie blond
mary brunnet
susan red
christine blackI want to get this output
angie blond
mary brunnet
susan redI write
grep --file=file1.txt file2.txtand i get no results
i also wrote
cat file1.txt|while read line... (19 Replies)
Discussion started by: FelipeAd
19 Replies
6. Shell Programming and Scripting
Hi Guys,
I have a small script which greps for the username reading from stdinput.
./file.sh pattern
pattern=$1
grep "blah blah.*$pattern" /home/user/log.txt
Instead of typing the pattern everytime i want to read the pattern from a file inside the shell script and execute the... (5 Replies)
Discussion started by: Irishboy24
5 Replies
7. Shell Programming and Scripting
Hi,
I'm trying to read a fille into a loop and grep for a string and print the last field of the string in the second file. Then redirect the output to another file but keeping the output in the same order as the original file.
I've tried using the following but the ouput from this does not... (3 Replies)
Discussion started by: elmesy
3 Replies
8. UNIX for Dummies Questions & Answers
Hi,
I have a number of files containing the information below.
"""""
Fundallinfo
6.3950 14.9715 14.0482
"""""
I would like to grep for Fundallinfo and use it to read the next line? I ideally would like to read the three numbers that follow in the next line and... (2 Replies)
Discussion started by: Paul Moghadam
2 Replies
9. UNIX for Beginners Questions & Answers
Hi All,
I am having a job and I need to send email when the job is running. On any other case (success,fail) I don't needed to send email. I check with BMC they told they dont have that in the version I am using.
So I created a dependent job and grepped for the status and sent email. My... (1 Reply)
Discussion started by: arunkumar_mca
1 Replies
10. UNIX for Advanced & Expert Users
I have a very big input file <inputFile1.txt> which has list of mobile no
inputFile1.txt
3434343
3434323
0970978
85233
... around 1 million records
i have another file as inputFile2.txt which has some log detail big file
inputFile2.txt
afjhjdhfkjdhfkd df h8983 3434343 | 3483 | myout1 |... (3 Replies)
Discussion started by: reldb
3 Replies
LEARN ABOUT OSX
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)