Home • About Us • A-Z Index • Search * Contact Us • Register • Login • Press • Shop

The Open Brand -- Problem Reporting and Interpretations System

Problem Report 2543 Details

Help Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges

This page provides all information on Problem Report 2543.

Report 2543 Actions

    Problem Report Number 2543
    Submitter's Classification Specification problem
    State Resolved
    Resolution Temporary Interpretation (TIN)
    Problem Resolution ID TIN.X.0131
    Raised 2008-12-19 07:29
    Updated 2009-01-05 14:16
    Published 2009-01-05 14:16
    Product Standard Commands and Utilities V4 (UNIX 03)
    Certification Program The Open Brand certification program
    Test Suite VSC version 5.2.12
    Test Identification /tset/POSIX.upe/more/more.ex 17,61,86,98,99,101
    Specification Shell and Utilities Issue 6
    Location in Spec http://www.opengroup.org/onlinepubs/000095399/utilities/more.html
    Problem Summary Inconsistency in specification of '-e' option to more(1) utility.
    Problem Text The specification of the more(1) utility contains an apparent inconsistency with regard to the '-e' command line option. In the
    OPTIONS section for -e:

    "By default, more shall exit immediately after writing the last line of the last file in the argument list. If the -e option is
    specified:
    1. If there is only a single file in the argument list and that file was completely displayed on a single screen, more shall exit
    immediately after writing the last line of that file.
    2. Otherwise, more shall exit only after reaching end-of-file on the last file in the argument list twice without an intervening
    operation. See the EXTENDED DESCRIPTION section."

    However, in the EXTENDED DESCRIPTION section:

    "For all files but the last (including standard input if no file was specified, and for the last file as well, if the -e option was not
    specified), when more has written the last line in the file, more shall prompt for a user command."

    The EXTENDED DESCRIPTION is consistent with the OPTIONS insofar as "for all files but the last file, when more has written the
    last line in the file, more shall prompt for a user command." However the parenthetical statement contains an apparent
    contradiction "and for the last file as well, if the -e option was not specified." The OPTIONS section indicates this parenthetical
    statement should read "and for the last file as well, if the -e option was specified" (note the removal of "not").

    The interpretation of the above affects the outcome of the following tests (which currently expect more(1) to wait for
    additional commands after the last line of the last file despite the absence of the -e option):

    VSC 5.2.12
    /tset/POSIX.upe/more/more.ex 17,61,86,98,99,101
    Test Output ***********************************************************************
    /tset/POSIX.upe/more/more.ex 17 Failed


    Test Information:
    Assertion #17 (C): The -e option causes more to exit at eof
    Expected exit code = 0; Received 2
    Standard error isn't empty
    Contents of out.stderr:
    termin: I/O resynchronization failed

    ***********************************************************************

    **********************************************************************
    /tset/POSIX.upe/more/more.ex 61 Failed


    Test Information:
    Assertion #61 (C): When stdout is a terminal, scrolling exits at end
    of last file
    Expected exit code = 0; Received 127

    ***********************************************************************


    ***********************************************************************
    /tset/POSIX.upe/more/more.ex 86 Failed


    Test Information:
    Assertion #86 (C): The '' command returns to position before last
    large movement
    Expected exit code = 0; Received 127
    Expecting line 34, was line not-found
    Command failed: 'checkline more_in_1 "34"'

    ***********************************************************************

    ***********************************************************************
    /tset/POSIX.upe/more/more.ex 98 Failed


    Test Information:
    Assertion #98 (C): The ?pattern command searches backwards
    Expected exit code = 0; Received 127
    Expecting line 47, was line not-found
    Command failed: 'checkline more_in_1 47'

    ***********************************************************************


    ***********************************************************************
    /tset/POSIX.upe/more/more.ex 99 Failed


    Test Information:
    Assertion #99 (C): The command ?pattern finds the first line matching
    pattern by default
    Expected exit code = 0; Received 127
    Expecting line 49, was line not-found
    Command failed: 'checkline more_in_1 49'

    ***********************************************************************

    ***********************************************************************
    /tset/POSIX.upe/more/more.ex 101 Failed


    Test Information:
    Assertion #101 (C): The ? command with a null RE repeats the last
    search
    Expected exit code = 0; Received 127
    Expecting line 48, was line not-found
    Command failed: 'checkline more_in_1 48'

    ***********************************************************************

    Review Information

    Review Type SA Review
    Start Date 2008-12-19 07:29
    Last Updated 2009-01-05 14:15
    Completed 2009-01-05 14:15
    Status Complete
    Review Resolution Temporary Interpretation (TIN)
    Review Conclusion This appears to be a contradiction in the standard. A temporary
    interpretation is granted pending the issue being investigated further
    by the working group.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority