Home • Explore • Blog • CI
☰



man-pages
4th chunk of `hd.man`
415115dffea022d0bbd34e09536f3ce77ebfd0ddb109a0240000000100000a93

       specified. Conditions, if present, are evaluated prior
       to highlighting.

       _L[color_unit_1,color_unit_2,...,color_unit_n]

       The full syntax of a color unit is as follows:

       [!]COLOR[:VALUE][@OFFSET_START[-END]]

       !
           Negate the condition. Please note that it only makes
           sense to negate a unit if both a value/string and an
           offset are specified. In that case the respective
           output string will be highlighted if and only if the
           value/string does not match the one at the offset.

       COLOR
           One of the 8 basic shell colors.

       VALUE
           A value to be matched specified in hexadecimal, or
           octal base, or as a string. Please note that the
           usual C escape sequences are not interpreted by
           hexdump inside the color_units.

       OFFSET
           An offset or an offset range at which to check for a
           match. Please note that lone OFFSET_START uses the
           same value as END offset.

   Counters
       The default and supported byte counts for the conversion
       characters are as follows:

       %_c, %_p, %_u, %c
           One byte counts only.

       %d, %i, %o, %u, %X, %x
           Four byte default, one, two and four byte counts
           supported.

       %E, %e, %f, %G, %g
           Eight byte default, four byte counts supported.

       The amount of data interpreted by each format string is
       the sum of the data required by each format unit, which
       is the iteration count times the byte count, or the
       iteration count times the number of bytes required by
       the format if the byte count is not specified.

       The input is manipulated in blocks, where a block is
       defined as the largest amount of data specified by any
       format string. Format strings interpreting less than an
       input block’s worth of data, whose last format unit both
       interprets some number of bytes and does not have a
       specified iteration count, have the iteration count
       incremented until the entire input block has been
       processed or there is not enough data remaining in the
       block to satisfy the format string.

       If, either as a result of user specification or hexdump
       modifying the iteration count as described above, an
       iteration count is greater than one, no trailing
       whitespace characters are output during the last
       iteration.

       It is an error to specify a byte count as well as
       multiple conversion characters or strings unless all but
       one of the conversion characters or strings is _a or _A.

       If, as a result
Title: Hexdump Color Highlighting Syntax and Conversion Character Byte Counts
Summary
This section continues the explanation of hexdump's color highlighting syntax, detailing how to specify colors, values to match, and offsets at which to check for matches. It also defines the default and supported byte counts for various conversion characters like %c, %d, %f, etc., and explains how the amount of data interpreted by each format string is calculated. The section also describes how hexdump manipulates input in blocks and adjusts iteration counts to process the entire block, and it outlines rules regarding whitespace output and specifying byte counts with multiple conversion characters.