INSPECT(1) User Commands INSPECT(1)NAME
inspect - Boost code inspection tool
SYNOPSIS
inspect [-cvs] [-text] [-brief] [options...]
DESCRIPTION
It is not uncommon for various common errors or guideline violations to creep into the Boost libraries. The inspect program detects and
reports several common problems. It can be used to scan a proposed Boost submission to identify various failures.
The program is run in the directory to be scanned for errors. Sub-directories are also included in the scan.
If the first program argument is -cvs, only files and directories in the CVS tree of the current directory are scanned. Otherwise all files
and sub-directories are included in the scan.
Options:
-license
-copyright
-crlf
-link
-path_name
-tab
-ascii
-minmax
-unnamed
The default is to have all checks on; otherwise options specify desired checks.
SEE ALSO
The full documentation for inspect is maintained in HTML; see /usr/share/doc/libboostX.Y-doc/HTML/tools/inspect/index.html
inspect July 2009 INSPECT(1)
Check Out this Related Man Page
BOWTIE2-INSPECT(1) User Commands BOWTIE2-INSPECT(1)NAME
bowtie2-inspect - extracts information from a bowtie2 index
SYNOPSIS
bowtie2-inspect [options]* <bt2_base>
DESCRIPTION
Bowtie 2 version 2.0.0-beta6 by Ben Langmead (blangmea@jhsph.edu)
<bt2_base>
bt2 filename minus trailing .1.bt2/.2.bt2
By default, prints FASTA records of the indexed nucleotide sequences to standard out. With -n, just prints names. With -s, just
prints a summary of the index parameters and sequences. With -e, preserves colors if applicable.
OPTIONS
-a/--across <int>
Number of characters across in FASTA output (default: 60)
-n/--names
Print reference sequence names only
-s/--summary
Print summary incl. ref names, lengths, index properties
-e/--bt2-ref
Reconstruct reference from .bt2 (slow, preserves colors)
-v/--verbose
Verbose output (for debugging)
-h/--help
print detailed description of tool and its options
--help print this usage message
64-bit Built on lxcsid Fri Jun 1 20:13:13 UTC 2012 Compiler: gcc version 4.7.0 (Debian 4.7.0-8) Options: -O3-m64-msse2-funroll-loops
-g3 Sizeof {int, long, long long, void*, size_t, off_t}: {4, 8, 8, 8, 8, 8}
bowtie2-inspect version 2.0.0-beta6 June 2012 BOWTIE2-INSPECT(1)
What is the easiest way to inspect the bytes stored in a file?
Ideally, If my file was 10 bytes each of which had only the high bit set, I'd be able to browse for it and get output like this:
01 - 10000000
02 - 10000000
03 - 10000000
04 - 10000000
05 - 10000000
06 - 10000000
07 -... (7 Replies)
"C++ Execution Inspection" is the best term I could coin for what it is I'd like to do. Suggestions from anyone who has done programming in C++ on Linux are welcome.
I was taught C++ in classrooms that used MS Visual Studio a few years ago. Visual Studio had a debugging mode that made it really... (1 Reply)
In a SCO Unix shop, I am working on the following script to move any file to its same location on the target machine (called 'othersy' here):
pwd=`pwd`
for i in "$@"
do
echo " $i "
if ; then echo 1; else echo 0; fi
rcp -p $i othersy:$pwd/$i
echo "Finished with ^ If I find a file... (4 Replies)
i have a unique scenario id like help with.
im currently running this command and it does what i want:
printf '%s\n' "${RawContent}" | awk '/## Beginning Stages ##/,/## Ending Stages ##/' | awk '!/^#.*\!|^#\!|DefaultError/'
Can this be shortened? I'm looking for something portable as... (8 Replies)