WG15 Defect Report Ref: 9945-2-115
Topic: mailx visual command edits messages in sequence.


This is an approved interpretation of 9945-2:1993.

.

Last update: 1997-05-20


								9945-2-115

 _____________________________________________________________________________

	Topic:                  mailx visual command edits messages in sequence.
	Relevant Sections:      4.40.7.2.38

Defect Report:
-----------------------

	Date: Thu, 20 Apr 1995 16:11:50 -0700
	From: [email protected] (ken dawson)


Dear Standards Board,

        I would like to request a formal interpretation on the following
issue concerning the mailx utility in POSIX.2.


In section 4.40.7.2.38 (Edit Messages with full-screen editor), the
Extended Description of the mailx command, (P354, L6803-6806), it says:

    Synopsis:    v[isual] [msglist]

    Edit the given messages with a screen editor.  The messages shall be
    placed in a temporary file and the utility named by the VISUAL
    variable (see 4.40.5.3) shall be invoked to edit the file.  The
    default editor shall be vi.

While this language is clear, and corresponds well with the language in
the SVID (mailx(au_cmd, p 6-50)), the actual historical behavior of this
command should be expressed as follows:

    Edit the given messages.  Each message shall be placed in a temporary
    file and the utility named by the VISUAL variable (see 4.40.5.3)
    shall be invoked to edit each file in sequence.  The default editor
    shall be vi.

I believe that this variance from actual historic practice was not
intended.  The rationale for mailx seems to carefully point out the cases
where the standard differs from historic practice, but does not mention
this issue.


Interpretation response
------------------------
The standard states the behavior for the visual command in mailx, and 
conforming implementations must conform to this.  However, concerns have 
been raised about this which are being referred to the sponsor.



Rationale:
None

Forwarded to Interpretations group: Apr 21 1995
Proposed resolution circulated: May 16th
Comments due: June 15th
Date Finalised: June 16th