Defect in XCU mailx

[Gunnar Ritter <yyyyyyyyyyyyy@xxxxxxxxxxxxxxxxxxxxx>]

@ Page 0 Line 0 Section mailx Comment []

Problem:
If a 'next' command follows a 'hold' command in mailx, traditional
implementations display the next message following the one the 'hold'
applied to, as if the holded message had been printed. This makes sense
since the 'hold' usually implies that the user knows what is in the
message and does not wish to view it again immediately. But the behavior
apparently conflicts with POSIX as the description states that the 'next'
command may only advance if the current message has been written before,
which is not the case with 'hold'.

Action:
Update the description of the 'next' command such that 'hold' makes it
also advance to the following message.