1 .TH SHOW %manext1% 2016-03-24 "%nmhversion%"
6 show \- show (display) nmh messages
20 .RB [ \-header " | " \-noheader ]
21 .RB [ \-checkmime " | " \-nocheckmime ]
22 .RB [ \-concat " | " \-noconcat ]
30 lists each of the specified messages to the standard output
31 (typically, the terminal).
33 By default, text (non-MIME) messages are filtered and displayed by
38 This command will display text
39 messages in a nice, uniform format. It also allows you to configure
40 the format of the displayed messages and which headers fields are
43 manual page for the details about this
44 command. This default can be changed by defining the
46 profile component. Any switches not recognized by
53 passed along to that program. To override the default and the
55 profile component, use the
63 program to list the messages with no reformatting. Normally, this
64 program is specified as the
68 rather than using a command line switch.
70 By default, non-text messages (MIME messages with multi-media
71 contents) are processed and displayed by the
77 manual page for details
78 about this command. This default can changed by defining the
80 profile component. Any switches not recognized
83 are passed along to that program. To override this
86 profile component, use the
91 Note that in some cases,
95 even for textual contents. This will happen for text messages that
96 specify a transfer encoding (such as MIME quoted-printable or
97 base64) or specify a character set that
100 can be displayed natively. The appropriate
102 environment variables
103 should be set to the terminal's native character set to avoid
104 gratuitous invocations of the
108 man page for details about these environment variables.
112 (set by default) instructs
115 test if any of the messages to be displayed are non-text (MIME)
116 messages. If any are non-text, they are displayed by the program
118 else they are displayed by the program
122 disables this test and instructs
126 regardless of whether
127 any of the messages are non-text (MIME) messages.
131 switch will disable any formatting or paging of
132 messages. It is equivalent to
136 It is still accepted, but should be considered (somewhat) obsolete.
142 to display a one-line
143 description of the message being shown. This description includes
144 the folder and the message number.
148 will concatenate all content under one pager. If you want each part to
149 displayed separately, you can override the default behavior with
152 If no `msgs' are specified, the current message is used. Although
153 it depends on the specific
157 in the default setup when more than one message is specified, you
158 will be prompted for a <RETURN> prior to listing each message.
159 Each message will be listed a page at a time, and when the end of
160 page is reached, the program will wait for a <SPACE> or <RETURN>.
161 If a <RETURN> is entered, it will print the next line, whereas
162 <SPACE> will print the next screenful.
164 If the standard output is not a terminal, no queries are made, and
165 each file is listed with a one-line header and two lines of
168 .RB \*(lq "show \-draft" \*(rq
169 will list the file <mh-dir>/draft if it
172 If the profile entry \*(lqUnseen\-Sequence\*(rq is present and
175 will remove each of the messages shown
176 from each sequence named by the profile entry.
180 .ta \w'%nmhetcdir%/ExtraBigFileName 'u
181 ^$HOME/.mh_profile~^The user profile
183 .SH "PROFILE COMPONENTS"
187 .ta \w'ExtraBigProfileName 'u
188 ^Path:~^To determine the user's nmh directory
189 ^Current\-Folder:~^To find the default current folder
190 ^Unseen\-Sequence:~^To name sequences denoting unseen messages
191 ^showproc:~^Program to show text (non-MIME) messages
192 ^showmimeproc:~^Program to show non-text (MIME) messages
202 .RB ` +folder "' defaults to the current folder"
203 .RB ` msgs "' defaults to cur"
209 If a folder is given, it will become the current folder. The last
210 message selected will become the current message.
214 switch doesn't work when `msgs' expands to more than
219 then this problem can
220 be circumvented by referencing the \*(lqmessagename\*(rq field in the
225 updates the user's context before showing the message.
228 will mark messages as seen prior to the user actually
229 seeing them. This is generally not a problem, unless the user relies
230 on the \*(lqunseen\*(rq messages mechanism, and interrupts
232 while it is showing \*(lqunseen\*(rq messages.
243 it does not actually run the
246 Hence, if you define your own
260 in the background with only its standard output piped to
261 another process, as in
269 show will go into a \*(lqtty input\*(rq state.
270 To avoid this problem, re-direct
272 diagnostic output as well.
284 show 2>&1 | imprint &