Hi,
I want to list only the file names which do not contain a specific keyword or search string.
OS: Solaris
Also is there any way ; through the same script I can save the output of search to a CSV (comma seperated) so that the file can be used for inventory purpose.
Any assistance will... (5 Replies)
Hi,I am new to shell scripting and i want to find the line numbers of matching braces.
The file contents are as follows
File XXX.dat
1 ( CLASS "FRUIT"
2 (TYPE "PERSISTENT")
3 (MESSAGE_TYPE "M")
4 (GET_REQRD "Y")
5 (SET_REQRD "Y")
6 )
7 ( CLASS... (3 Replies)
trying to use sed in finding a matching pattern in a file then deleting
the next line only .. pattern --> <ad-content>
I tried this but it results are not what I wish
sed '/<ad-content>/{N;d;}' akv.xml > akv5.xml
ex,
<Celebrant2First>Mickey</Celebrant2First>
<ad-content>
Minnie... (2 Replies)
Hi,
I have several block of text that I need to select, however this text may be spread over several lines and contains the '{' and '}' within it.
For e.g.,
ABC=100{
DEF = 200
{
GHI,
JKL
}
}
#2nd Block
123
{
456{78,910}}
}I am trying to figure out how to remove... (2 Replies)
Hi Guys,
I am new to the forum and to scripting so bear with me.
Thanks, Gary.
I have 3 files - file1, file2, file3
I am trying to come up with a script that will check the output of these files and if the 1st nine fields are matched in all 3 files, echo "The following string had been... (2 Replies)
Must be a bug or something. Whether I escape them or not, it will not work. No matter what I set the minimum and maximum to nothing gets caught. For instance:
find / -regex "/.{0, 50}.*" -maxdepth 1 or find / -regex "/.\{0, 50\}.*" -maxdepth 1 should pretty much catch everything residing within... (4 Replies)
Hi everyone:
I'm stuck at this point, could you guys please give me some hints about what I am doing wrong in the following script, I'm using sed for windows:
sed ^"$ {^
a^
STRINGTABLE DISCARDABLE^
BEGIN^
#define CLIENT_MODULE, "%CLIENT_MODULE%"^
#define CLIENT_ID, "%CLIENT_ID%"^... (1 Reply)
Hi friends.. I have many dirs in my working directory. Every dir have thousands of files (.jsp, .java, .xml..., etc). So I am working with an script to find every file recursively within those directories and subdirectories ending with .jsp or .java which contains inside of it, the the pattern... (3 Replies)
i need to search for user belonging to group 'macusr' and the extract the user name .
i am able to write a oneliner for this using awk + sed + tr
i am using tr to chop off '()' from the output. but i want to use it in sed itself . can someone please help me with that
file contents
... (7 Replies)
Hi,
I have below command in one of the script. Can you please let me know what does the curly braces do over here \{1,\}. The remaining part of the code atleast I am able to understand.
sed -n 's/.*\-\()\{1,\}\)\-.*/\1/p' (13 Replies)
Discussion started by: tostay2003
13 Replies
LEARN ABOUT DEBIAN
tex2xindy
tex2xindy(1) xindy tex2xindy(1)NAME
tex2xindy - a preprocessor of the xindy index processor
SYNOPSIS
tex2xindy [-o] [attr_file]
DESCRIPTION
tex2xindy transforms a LaTeX index file ".idx" (or an ".aux" file) into a xindy raw index file.
It is a filter that reads from stdin a file in the input format of LaTeX's raw index file, i.e., with "indexentry" tags. It outputs on
stdout a xindy raw index file, i.e., with "indexentry" clauses.
If the option -o is not specified, tex2xindy handles ^^-notation of TeX and outputs the octet that is represented: "^^ab" in the input gets
output as the octet 0xab. If "^^^^abcd" or "^^^^^^^^abcdefab" are detected, they are output as is.
If the option -o is specified, tex2xindy operates in Omega mode and handles its ^^-notation: Then "^^ab", "^^^^abcd", and
"^^^^^^^^abcdefab" represent Unicode characters with code points 0xab, 0xabcd, and 0xabcdefab respectively. They are output in UTF-8
encoding.
If the optional argument attr_file is specified, tex2xindy writes all index key attributes into this file.
DEFICITS
This program was written since it was not easily possible to extract the parser from the old makeindex system. Therefore it does not find
all errors in the input as the makeindex(1) version.
Additionally it uses only the default input specifiers of makeindex(1). If other input specifiers (cf. manual page of makeindex(1)) are
needed, the input specifiers (starting from the pattern "KEYWORD", see below) must be changed and the program must be recompiled.
The particular missing feature is configuration of the quote and the actual characters, maybe also the escape, subitem (level), and encap
characters. Argument and range delimiters seem to be less of a problem.
In fact, input markup handling (and thus tex2xindy) should be incorporated into the xindy kernel, to be able to specify configuration in
xindy style files.
SEE ALSO texindy(1), xindy(1), makeindex(1)AUTHOR
Roger Kehr, Institut fuer Theoretische Informatik, TU Darmstadt
COPYRIGHT AND LICENSE
Copyright (c) 1996,1997 Roger Kehr. Copyright (c) 2006 Joachim Schrod.
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation,
Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
Version 1.24 2010-05-10 tex2xindy(1)