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

The Open Brand -- Problem Reporting and Interpretations System

Problem Report 0535 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 0535.

Report 0535 Actions

    Problem Report Number 0535
    Submitter's Classification Minor System Fault
    State Resolved
    Resolution Minor System Fault (MSF)
    Problem Resolution ID MSF.X.0026
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published 1996-07-11 08:00
    Expiry Date 1997-01-04
    Product Standard Commands and Utilities V2 (UNIX 95)
    Certification Program The Open Brand certification program
    Test Suite VSC version 4.1.5
    Test Identification POSIX.upe/vi 139
    Problem Summary MSF4C.00012 A MSF is requested because '.' does not repeat the 'p' commands.
    Problem Text
    A MSF is requested because '.' does not repeat the 'p' commands.

    Reference: MSF4C.00006

    There is a problem with the vi command on
    our system: '.' does not repeat a 'p' or 'P' command. To the
    best of our knowledge this is historical behavior. It's a bug
    that has always been in vi, but one that must be fixed to
    conform to POSIX.2.

    Adapted from MSF4Csan.00006:

    The test in question verifies the assertion:
    When [count] . is entered in command mode, then vi repeats the last
    command that changed the buffer and uses count as the number of
    iterations of the command being repeated. (Default 1 when count not
    specified) The values of current line and column are set as specified by
    the command which is repeated.
    TESTING REQUIREMENT:
    Test for each of the buffer changing commands !, &, <, >, ~,
    a, A, c, C, d, D, i, I, J, o, O, p, P, r, R, s, S, u, U, x and X.

    On our implementation the assertion fails for the "p" and "P"
    commands. This behavior (a failure to repeat a "p" or "P") is
    longstanding; according to Keith Bostic, it is the historical behavior
    of vi. Nevertheless, he views it as a bug, as do POSIX.2-1990, XPG4
    Issue 2, and (draft) POSIX.2b.

    We request a waiver on the grounds that this is a Minor System Fault.
    In support of this request we wish to point out that:
    (a) The current test suite, because of its own bug, does not exhibit
    this failure.
    (b) This is the historical behavior of the vi utility.
    (c) A workaround (using "p" or "P" instead of ".") is always available
    to the user.
    Test Output
    /tset/POSIX.upe/vi/vi_02.ex 1 Failed
    Test Information:
    Assertion #139 (C): count . command
    Note: The testing requirements include testing for the dot
    <LC> and
    ampersand commands. This violates historical practice and
    <LC> is
    expected to change in a future revision of POSIX.2, but it
    remains a normative requirement of the current standard.
    . fails for & or >
    diff of "vi_exp_1" and "vi_in_1":
    *** vi_exp_1 Sat Jun 29 08:33:23 1996
    --- vi_in_1 Sat Jun 29 08:33:41 1996
    *** 1,4 ****
    ! hXrX is filX xo xesx
    New line of file
    another line
    a few
    --- 1,4 ----
    ! hXrX is file xo xest
    New line of file
    another line
    a few
    . fails for p or P
    diff of "vi_exp_7" and "vi_in_7":
    *** vi_exp_7 Sat Jun 29 08:37:32 1996
    --- vi_in_7 Sat Jun 29 08:37:45 1996
    *** 1,5 ****
    filete to play with
    ! Here wHere e haveHere
    ! text a text filetext
    filete to play filetewith
    to play with
    --- 1,5 ----
    filete to play with
    ! Here wHere e have
    ! a text filetext
    filete to play filetewith
    to play with
    . fails for u
    diff of "vi_exp_10" and "vi_in_10":
    *** vi_exp_10 Sat Jun 29 08:39:07 1996
    --- vi_in_10 Sat Jun 29 08:39:26 1996
    *** 1,3 ****
    ! and here we have
    a text file
    to play with
    --- 1,3 ----
    ! Here we havand and and h
    a text file
    to play with
    Test Results:

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    A temporary waiver for a minor system fault is recommended.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Minor System Fault (MSF)
    Review Conclusion
    A Temporary Waiver is granted.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority