08-27-2012
I don't think than anybody can follow this without representative sample input, a definitive description of the process, and matching expected output.
Quote:
I am attempting to find the path /subject/grin* and replace it with /subject/$i
In this sentence, what is "it" ? Are you trying to rename the files or edit the contents of the files or what?
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
hi,
i need to replace a line a file with a new raw device location..
original file..
/opt/sybase/ASE1502/ASE-15_0/bin/dataserver \
-d/data/TST_AKS1/sybdevices/master.dat \
-e/logs/sybase/TST_AKS1/SFO_TST_AKS1.log \
-c/apps/sybase/ASE1502/ASE-15_0/TST_AKS1.cfg \... (2 Replies)
Discussion started by: aksaravanan
2 Replies
2. Shell Programming and Scripting
I have to update a paramater (dateMemLimit) present in a file, with a date (YYYYMMDD) equal to 5 days before the sysdate. The parameter will be in the following format.
dateMemLimit = 20091201
Please note the blank spaces present between 'dateMemLimit' &'=' and between '='... (4 Replies)
Discussion started by: rajesh8s
4 Replies
3. Shell Programming and Scripting
e.g.
/home/$USER/.config replace it with "" (empty)
Is this possible?
I think you should play a bit with sharps ## and sed:b: (2 Replies)
Discussion started by: hakermania
2 Replies
4. Shell Programming and Scripting
Hello all
I have a file with a lot of records...Each one have a ID like this:
000000001 LDR L -----nam--2200217Ia-45e0
000000001 891
000000001 892
000000001 893
and so on
then you have the second record:
000000002 LDR L -----nam--2200208Ia-15e0
000000002 891
000000002... (5 Replies)
Discussion started by: ldiaz2106
5 Replies
5. Shell Programming and Scripting
Hi,
I have two files
file1 :>
val="10"
port="localhost:8080"
httpadd="http:\\192.168.0.239"
file2 :>
val=${val}
port=${port}
httpadd=${httpadd}
fileloc=${fileloc}
file3(or file2) should have following output(input from fileone)
file3 (8 Replies)
Discussion started by: nitin.pathak
8 Replies
6. Emergency UNIX and Linux Support
Guys I have a big issue that I need to get fixed ASAP however I can not seem to find a way to do it. We started to use zones with Solaris 10 at work and we moved a zone from a SIT box to a DEV box. Problem is the software we have installed is looking at a /lcl/sit/apps/ path and it needs to look... (5 Replies)
Discussion started by: LRoberts
5 Replies
7. Shell Programming and Scripting
Hi All,
How can i find and replace the one path to another path with in the file.
For Example:
Search_path=/search/path
replace_path=/replace/path
I used the following command but not usefull, please help me regarding the same.
sed 's_/search/path_/replace/path_' file_name >... (6 Replies)
Discussion started by: nsyed.dw
6 Replies
8. Shell Programming and Scripting
Hi,
I have a file such that:
tart*)*98'bank'ksb64bank)(tart2d&f44bank
I want to replace to: (only between tart and bank)
tart*)*98'replaced'ksb64bank)(tart2d&f44replaced
Thanks. (6 Replies)
Discussion started by: tara123
6 Replies
9. Shell Programming and Scripting
Hi All,
I have a file as shown below: myFile.dat
#----------------------------------------------------------
dataFile
{
Name shiva;
location Delhi;
travelID IDNumber;
}
4
(
560065
700007
100001
200002
)... (8 Replies)
Discussion started by: linuxUser_
8 Replies
10. Shell Programming and Scripting
Hi,
I need to do find and replace, but the pattern is not full known.
for example,
my file has /proj/app-d1/sun or /data/site-d1/conf
here app-d1 and site-d1 is not constant. It may be different in different files. common part is /proj/xx/sun and /data/xxx/conf
i want to find where ever... (6 Replies)
Discussion started by: rbalaj16
6 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)