Thanks, Fixed for the next beta.
On Wed, Feb 5, 2014 at 3:18 PM, Nathan Weeks <[email protected]> wrote: > In the sh(1) man page distributed with ksh 2014-01-14 beta, it looks > like part of the text for the description of .sh.match was > inadvertently transplanted to the description of .sh.version: > > ===================================== > .sh.match > An indexed array which stores the most recent match and > sub-pattern matches after conditional pattern matches that match > and after variables expansions using the operators > ... > .sh.version > The current version of this shell. #, %, or /. The 0-th element > stores the complete match and the i-th. element stores the > i-th submatch. For // the array is two dimensional with the first > subscript indicating the most recent match and sub-pattern match > and > the second script indicating which match with 0 representing the > first match. The .sh.match variable becomes unset when the > variable > that has expanded is assigned a new value. > ===================================== > > -- > Nathan Weeks > IT Specialist > USDA-ARS Corn Insects and Crop Genetics Research Unit > http://weeks.public.iastate.edu/ > _______________________________________________ > ast-users mailing list > [email protected] > http://lists.research.att.com/mailman/listinfo/ast-users >
_______________________________________________ ast-users mailing list [email protected] http://lists.research.att.com/mailman/listinfo/ast-users
