1 .TH SHOW %manext1% "February 8, 2015" "%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
52 passed along to that program. To override the default and the
54 profile component, use the
62 program to list the messages with no reformatting. Normally, this
63 program is specified as the
66 .IR \&.mh\(ruprofile ,
67 rather than using a command line switch.
69 By default, non-text messages (MIME messages with multi-media
70 contents) are processed and displayed by the
76 manual page for details
77 about this command. This default can changed by defining the
79 profile component. Any switches not recognized
82 are passed along to that program. To override this
85 profile component, use the
90 Note that in some cases,
94 even for textual contents. This will happen for text messages that
95 specify a transfer encoding (such as MIME quoted-printable or
96 base64) or specify a character set that
99 can be displayed natively. The appropriate
101 environment variables
102 should be set to the terminal's native character set to avoid
103 gratuitous invocations of the
107 man page for details about these environment variables.
111 (set by default) instructs
114 test if any of the messages to be displayed are non-text (MIME)
115 messages. If any are non-text, they are displayed by the program
117 else they are displayed by the program
121 disables this test and instructs
125 regardless of whether
126 any of the messages are non-text (MIME) messages.
130 switch will disable any formatting or paging of
131 messages. It is equivalent to
135 It is still accepted, but should be considered (somewhat) obsolete.
141 to display a one\-line
142 description of the message being shown. This description includes
143 the folder and the message number.
145 If no `msgs' are specified, the current message is used. Although
146 it depends on the specific
150 in the default setup when more than one message is specified, you
151 will be prompted for a <RETURN> prior to listing each message.
152 Each message will be listed a page at a time, and when the end of
153 page is reached, the program will wait for a <SPACE> or <RETURN>.
154 If a <RETURN> is entered, it will print the next line, whereas
155 <SPACE> will print the next screenful.
157 If the standard output is not a terminal, no queries are made, and
158 each file is listed with a one\-line header and two lines of
161 .RB \*(lq "show \-draft" \*(rq
162 will list the file <mh\-dir>/draft if it
165 If the profile entry \*(lqUnseen\-Sequence\*(rq is present and
168 will remove each of the messages shown
169 from each sequence named by the profile entry.
173 .ta \w'%nmhetcdir%/ExtraBigFileName 'u
174 ^$HOME/\&.mh\(ruprofile~^The user profile
176 .SH "PROFILE COMPONENTS"
180 .ta \w'ExtraBigProfileName 'u
181 ^Path:~^To determine the user's nmh directory
182 ^Current\-Folder:~^To find the default current folder
183 ^Unseen\-Sequence:~^To name sequences denoting unseen messages
184 ^showproc:~^Program to show text (non-MIME) messages
185 ^showmimeproc:~^Program to show non-text (MIME) messages
195 .RB ` +folder "' defaults to the current folder"
196 .RB ` msgs "' defaults to cur"
201 If a folder is given, it will become the current folder. The last
202 message selected will become the current message.
206 switch doesn't work when `msgs' expands to more than
211 then this problem can
212 be circumvented by referencing the \*(lqmessagename\*(rq field in the
217 updates the user's context before showing the message.
220 will mark messages as seen prior to the user actually
221 seeing them. This is generally not a problem, unless the user relies
222 on the \*(lqunseen\*(rq messages mechanism, and interrupts
224 while it is showing \*(lqunseen\*(rq messages.
235 it does not actually run the
238 Hence, if you define your own
252 in the background with only its standard output piped to
253 another process, as in
261 show will go into a \*(lqtty input\*(rq state.
262 To avoid this problem, re\-direct
264 diagnostic output as well.
276 show 2>&1 | imprint &