DataMuseum.dk

top - download

    Length: 3666 (0xe52)
    Types: TextFile
    Names: »readmsg.1«

└─⟦a0efdde77⟧ Bits:30001252 EUUGD11 Tape, 1987 Spring Conference Helsinki
    └─ ⟦this⟧ »EUUGD11/euug-87hel/sec1/elm/doc/readmsg.1« 

TextFile

.TH READMSG 1L
.ad b
.SH NAME
readmsg - read messages from incoming mail
.SH SYNOPSIS
.B readmsg 
[\fB-p\fR]
[\fB-n\fR]
[\fB-f filename\fR]
[\fB-h\fR]
.br
.B readmsg
[\fB-p\fR]
[\fB-n\fR]
[\fB-f filename\fR]
[\fB-h\fR]
number [number ...]
.br
.B readmsg 
[\fB-p\fR]
[\fB-n\fR]
[\fB-f filename\fR]
[\fB-h\fR]
pattern
.br
.SH HP-UX COMPATIBILITY
.TP 10
Level:
HP-UX/CONTRIBUTED
.TP
Origin:
Hewlett-Packard
.SH DESCRIPTION
.I Readmsg
is a program that gives the \fBElm\fR user the functionality of
the mailx "~r" command from the editor of their choice.  There
are three different ways of using the program;
.P
First off, if you're actually creating a reply to a message
from within the \fBElm\fR system then \fIreadmsg\fR without any
arguments will include a summary of the headers and the body 
of the message being replied
to.  If you aren't currently editing a message the program will
return an error.
.P
Secondly, if you want to include certain messages, you can
specify them by listing their ordinal locations in the 
mail file (that is, their "message numbers")
up to 25 at a time.  The \fImeta-\fRnumber '$' is understood to mean
the last message in the mailfile.  Similarly, '*' is understood to
represent every message in the file (that is, 1-$)
.P
Finally, you can also specify a pattern that occurs in one of
the messages as a way of including it.  This pattern can be
typed in directly (no quotes) if the words are separated by a 
single space in the actual message.  The pattern matching is case
sensitive, so "Hello" and "hello" are NOT the same thing!!
.sp
.P
The \fB-f\fR flag indicates that you'd rather use the file specified
for the operations specified rather than the default mailbox (see
the way \fBElm\fR implements printing multiple messages for more
information on this...)
.P
The \fB-h\fR flag instructs the program to include the entire header
of the matched message or messages when displaying their
text.  (default is to display the From: Date: and Subject: lines
only)
.P
The \fB-n\fR flag instructs the program to exclude \fIall\fR
headers.  This is used mostly for extracting files mailed and
such.
.P
Finally, the \fB-p\fR flag indicates that the program should
put form-feeds (control-L) between message headers.
.sp
.SH "EXAMPLES"
First off, to use this from within \fBvi\fR to include the text of the 
current message at the end of the current message, you could
use the command;
.nf

	!!readmsg

.fi
(as you hit the 'G' the editor will put you at the bottom of the screen
with the '!' prompt).
.sp 2
Let's look at something more interesting, however;
.sp
Suppose you have the mailfile;
.nf

   From joe Jun 3 1986 4:45:30 MST
   Subject: hello
   
   Hey Guy!  Wanta go out and have a milk this evening?
   
   Joe
   
   From john Jun 3 1986 4:48:20 MST
   Subject: Dinner at Eight
   From: John Dinley <xyz!john>

   Remember you should show up about eight, okay?

		   - John D -

   From xxzyz!cron Jun 3 1986 5:02:43 MST

   Cannot connect to server: blob
   Job 43243 deleted from queue.
   
.fi
The following commands will result in;
.nf

  $ readmsg 2		
  [ display the second message, from John ]

  $ readmsg 		
  [ an error, unless we're calling from \fBElm\fR ]

  $ readmsg BLOB	
  [ no match - case sensitive! ]

  $ readmsg -h connect to server 
  [ displays third message, including headers ]

.fi
.SH FILES
/usr/mail/<username>   		The incoming mail
.br
$home/.readmsg			The temp file from \fBElm\fR
.SH AUTHOR
Dave Taylor, Hewlett-Packard Laboratories
.SH SEE\ ALSO
newmail(1L), Elm(1L)
.SH BUGS
The '*' metacharacter doesn't always work as expected!
.br
Perhaps the pattern matching should be case insensitive?