|
DataMuseum.dkPresents historical artifacts from the history of: DKUUG/EUUG Conference tapes |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about DKUUG/EUUG Conference tapes Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - downloadIndex: T r
Length: 3739 (0xe9b) Types: TextFile Names: »readmsg.1«
└─⟦9ae75bfbd⟧ Bits:30007242 EUUGD3: Starter Kit └─⟦4fd8323b9⟧ »EurOpenD3/mail/elm2.3.tar.Z« └─⟦698c4f91f⟧ └─⟦this⟧ »doc/readmsg.1«
.TH READMSG 1L "Elm Version 2.3" "USENET Community Trust" .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 DESCRIPTION .I Readmsg is a program that gives the \fIelm\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 \fIelm\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. .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 \fIelm\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 \fIelm\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? .SH BUG REPORTS TO Syd Weinstein elm@DSI.COM (dsinc!elm) .SH COPYRIGHTS .ps 18 \fB\(co\fR\s12 Copyright 1986, 1987 by Dave Taylor .br .ps 18 \fB\(co\fR\s12 Copyright 1988, 1989, 1990 by The USENET Community Trust