1 .TH SHOW %manext1% "June 6, 2012" "%nmhversion%"
6 show \- show (display) messages
18 .RB [ \-header " | " \-noheader ]
19 .RB [ \-checkmime " | " \-nocheckmime ]
29 lists each of the specified messages to the standard output
30 (typically, the terminal).
32 By default, text (non-MIME) messages are filtered and displayed by
37 This command will display text
38 messages in a nice, uniform format. It also allows you to configure
39 the format of the displayed messages and which headers fields are
42 manual page for the details about this
43 command. This default can be changed by defining the
45 profile component. Any switches not recognized by
48 passed along to that program. To override the default and the
50 profile component, use the
58 program to list the messages with no reformatting. Normally, this
59 program is specified as the
62 .IR \&.mh\(ruprofile ,
63 rather than using a command line switch.
65 By default, non-text messages (MIME messages with multi-media
66 contents) are processed and displayed by the
72 manual page for details
73 about this command. This default can changed by defining the
75 profile component. Any switches not recognized
78 are passed along to that program. To override this
81 profile component, use the
86 Note that in some cases,
90 even for textual contents. This will happen for text messages that
91 specify a transfer encoding (such as MIME quoted-printable or
92 base64) or specify a character set that
95 can be displayed natively. The appropriate
98 should be set to the terminal's native character set to avoid
99 gratuitous invocations of the
103 man page for details about these environment variables.
107 (set by default) instructs
110 test if any of the messages to be displayed are non-text (MIME)
111 messages. If any are non-text, they are displayed by the program
113 else they are displayed by the program
117 disables this test and instructs
121 regardless of whether
122 any of the messages are non-text (MIME) messages.
126 switch will disable any formatting or paging of
127 messages. It is equivalent to
131 It is still accepted, but should be considered (somewhat) obsolete.
137 to display a one\-line
138 description of the message being shown. This description includes
139 the folder and the message number.
141 If no `msgs' are specified, the current message is used. Although
142 it depends on the specific
146 in the default setup when more than one message is specified, you
147 will be prompted for a <RETURN> prior to listing each message.
148 Each message will be listed a page at a time, and when the end of
149 page is reached, the program will wait for a <SPACE> or <RETURN>.
150 If a <RETURN> is entered, it will print the next line, whereas
151 <SPACE> will print the next screenful.
153 If the standard output is not a terminal, no queries are made, and
154 each file is listed with a one\-line header and two lines of
157 .RB \*(lq "show \-draft" \*(rq
158 will list the file <mh\-dir>/draft if it
161 If the profile entry \*(lqUnseen\-Sequence\*(rq is present and
164 will remove each of the messages shown
165 from each sequence named by the profile entry.
169 .ta \w'%etcdir%/ExtraBigFileName 'u
170 ^$HOME/\&.mh\(ruprofile~^The user profile
172 .SH "PROFILE COMPONENTS"
176 .ta \w'ExtraBigProfileName 'u
177 ^Path:~^To determine the user's nmh directory
178 ^Current\-Folder:~^To find the default current folder
179 ^Unseen\-Sequence:~^To name sequences denoting unseen messages
180 ^showproc:~^Program to show text (non-MIME) messages
181 ^showmimeproc:~^Program to show non-text (MIME) messages
191 .RB ` +folder "' defaults to the current folder"
192 .RB ` msgs "' defaults to cur"
197 If a folder is given, it will become the current folder. The last
198 message selected will become the current message.
202 switch doesn't work when `msgs' expands to more than
207 then this problem can
208 be circumvented by referencing the \*(lqmessagename\*(rq field in the
213 updates the user's context before showing the message.
216 will mark messages as seen prior to the user actually
217 seeing them. This is generally not a problem, unless the user relies
218 on the \*(lqunseen\*(rq messages mechanism, and interrupts
220 while it is showing \*(lqunseen\*(rq messages.
231 it does not actually run the
234 Hence, if you define your own
248 in the background with only its standard output piped to
249 another process, as in
257 show will go into a \*(lqtty input\*(rq state.
258 To avoid this problem, re\-direct
260 diagnostic output as well.
272 show 2>&1 | imprint &