anchor.diff:  .Command-Line Flags
   [width="100%",cols="2,5,5",options="header"]
   |===
  -| Flag | Argument | Meaning
  -| -f | name of the input file(s) | May include wildcards.
  -| -o | name of the output file to hold copies of all duplicated records found | If not given, then assumes the same as the input file but with a .OUT extension. Will be overwritten if already exists.
  -| --verbose | | Displays detailed information (statistics).
  -| --debug | | Displays how the specification file was interpreted, among other things.
  -| -l | name of a log file to use | Will be appended to the end if already exists.
  -| -s | name of the specification file | If not given, then assumes the same as the input file but with a .INI extension.
  -| --help | | Get help on these flag definitions.
  +| Flag      | Argument                       | Meaning
  +| -f        | name of the input file(s)      | May include wildcards.
  +| -o        | name of the output file to hold copies of all duplicated records found | If not given, then assumes the same as the input file but with a .OUT extension. Will be overwritten if already exists.
  +| --verbose |                                | Displays detailed information (statistics).
  +| --debug   |                                | Displays how the specification file was interpreted, among other things.
  +| -l        | name of a log file to use      | Will be appended to the end if already exists.
  +| -s        | name of the specification file | If not given, then assumes the same as the input file but with a .INI extension.
  +| --help    |                                | Get help on these flag definitions.
   |===
   
  -If multiple files are specified (via wildcards), the results will be combined in a single output file. So, be sure to specify `PrependFileName=Y` in the INI file (see below). Otherwise, it will be hard to backtrack where the duplicates were found. Also, note that the search for duplicates does not span input files. If the same key value occurs in two different files, it is not considered a duplication. Only if the key value is repeated within the same files is it considered a duplication.
  +If multiple files are specified (via wildcards), the results will be combined in a single output file. 
  +So, be sure to specify `PrependFileName=Y` in the INI file (see below). 
  +Otherwise, it will be hard to backtrack where the duplicates were found. 
  +Also, note that the search for duplicates does not span input files. 
  +If the same key value occurs in two different files, it is not considered a duplication. 
  +Only if the key value is repeated within the same file is it considered a duplication.
   
   Redirecting the console output to a log file (`>> some.log`) is functionally equivalent to using the `-l` flag.
   
   
   == Specification Files
   
  -A simple INI file tells DupSeeker how to interpret the input file. It also controls how the tool does the dup-seeking, and it controls how the findings are reported.
  +A simple INI file tells DupSeeker how to interpret the input file. 
  +It also controls how the tool does the dup-seeking, and it controls how the findings are reported.
   
   	[File]
   	Type=csv
  
positive.code: 
  A command-line utility that searches a (delimited) file for duplicate values in a certain column, and then filters the information down to only those duplicated lines.
  
  For example, the pirate-words.csv file in the examples folder lists the word "mutiny" on line 12 and again on line 37. This utility will find that redundancy (among others).
  
  The pirate-words.csv file is a trivial example; however, this tool was designed to handle files with millions of records. The idea is that this tool is used as a first step towards further analysis (in Excel, or whatever). Where Excel might choke on trying to process a 5-million record file, directly, if that file is first filtered down to just a few hundred thousand records (the ones with the dups), then Excel can more easily process that.
  
  
  == Getting Started
  
negative.code: 
  * For either section, set the column number to be considered equal to the value, or values, to be matched (comma separated).
  
  In our pirate-words.csv example, the fourth column classifies each entry as being either a "word", "phrase", "name", or "title". 
  Let's say that we only want DupSeeker to look for duplicates among the "word" and "phrase" entries. 
  We can use an [Include] section that says to only include lines where column 4 equals "word,phrase". 
  Alternately, we could use an [Exclude] section that says to exclude lines where column 4 equals either "name" or "title". 
  That will accomplish the same thing, in this case.
  
  
  == See Also
  