X-Git-Url: https://diplodocus.org/git/nmh/blobdiff_plain/d1cb667bddf8d1c5c0721fc7ab642c22946baf1f..d6e398f9c:/man/mhshow.man?ds=sidebyside diff --git a/man/mhshow.man b/man/mhshow.man index 04a88c4f..b6fe8838 100644 --- a/man/mhshow.man +++ b/man/mhshow.man @@ -1,4 +1,4 @@ -.TH MHSHOW %manext1% "April 30, 2012" "%nmhversion%" +.TH MHSHOW %manext1% "March 16, 2014" "%nmhversion%" .\" .\" %nmhwarning% .\" @@ -18,8 +18,6 @@ mhshow \- display MIME messages .RB [ \-type .IR content ] \&... -.RB [ \-serialonly " | " \-noserialonly ] -.RB [ \-pause " | " \-nopause ] .RB [ \-form .IR formfile ] .RB [ \-rcache @@ -38,11 +36,11 @@ message or collection of messages. .PP .B mhshow manipulates multi-media messages as specified in -RFC\-2045 thru RFC\-2049. Currently +RFC 2045 to RFC 2049. Currently .B mhshow only supports encodings in message bodies, and does not support the encoding of -message headers as specified in RFC\-2047. +message headers as specified in RFC 2047. .PP By default .B mhshow @@ -92,7 +90,7 @@ switch will not prevent the content from being acted upon. .PP A content specification consists of a content type and a subtype. The initial list of \*(lqstandard\*(rq content types and subtypes can -be found in RFC\-2046. +be found in RFC 2046. .PP A list of commonly used contents is briefly reproduced here: .PP @@ -224,38 +222,43 @@ The display string may contain the following escapes: .PP .RS 5 .nf -.ta \w'%F 'u -%a Insert parameters from Content-Type field -%e exclusive execution -%f Insert filename containing content -%F %e, %f, and stdin is terminal not content -%l display listing prior to displaying content -%p %l, and ask for confirmation -%s Insert content subtype -%d Insert content description -%% Insert the character % +.ta \w'%F 'u +%a Insert parameters from Content-Type field +%{parameter} Insert the parameter value from the Content-Type field +%f Insert filename containing content +%F %f, and stdin is terminal not content +%l display listing prior to displaying content +%s Insert content subtype +%d Insert content description +%% Insert the character % .fi .RE .PP -For those display strings containing the e- or F-escape, -.B mhshow +.B Mhshow will -execute at most one of these at any given time. Although the F-escape -expands to be the filename containing the content, the e-escape has no -expansion as far as the shell is concerned. +execute at most one display string at any given time, and wait for the +current display string to finish execution before executing the next +display string. .PP -When the p-escape prompts for confirmation, typing INTR (usually -control-C) will tell -.B mhshow -not to display that content. -The p-escape can be disabled by specifying the switch -.BR \-nopause . -Further, when -.B mhshow -is display a content, typing QUIT (usually -control-\\) will tell -.B mhshow -to wrap things up immediately. +The {parameter} escape is typically used in a command line argument +that should only be present if it has a non-null value. Its value +will be wrapped with single quotes if the escape is not so wrapped. +Shell parameter expansion can construct the argument only when it is +non-null, e.g., +.PP +.RS 5 +.nf +mhshow-show-text/html: charset=%{charset}; + w3m ${charset:+-I $charset} -T text/html %F +.fi +.RE +.PP +That example also shows the use of indentation to signify continuation: +the two text lines combine to form a single entry. Note that when +dealing with text that has been converted internally by +.IR iconv (3), +the \*(lqcharset\*(rq parameter will reflect the target character set +of the text, rather than the original character set in the message. .PP Note that if the content being displayed is multipart, but not one of the subtypes listed above, then the f- and F-escapes expand to multiple @@ -264,15 +267,18 @@ redirected from the terminal to the content. .PP If a display string is not found, .B mhshow -has several default values: +behaves as if these profile entries were supplied and supported: .PP .RS 5 .nf -mhshow-show-text/plain: %pmoreproc '%F' -mhshow-show-message/rfc822: %pshow -file '%F' +mhshow-show-text/plain: %lmoreproc %F +mhshow-show-message/rfc822: %lshow -file %F .fi .RE .PP +Note that \*(lqmoreproc\*(rq is not supported in user profile display +strings. +.PP If a subtype of type text doesn't have a profile entry, it will be treated as text/plain. .PP @@ -296,28 +302,38 @@ Example entries might be: .RS 5 .nf mhshow-show-audio/basic: raw2audio 2>/dev/null | play -mhshow-show-image: xv '%f' +mhshow-show-image: xv %f mhshow-show-application/PostScript: lpr -Pps .fi .RE .PP -Note that when using the f- or F-escape, it's a good idea to use -single-quotes around the escape. This prevents misinterpretation by -the shell of any funny characters that might be present in the filename. +If an f- or F-escape is not quoted with single quotes, its expansion +will be wrapped with single quotes. .PP Finally, .B mhshow will process each message serially\0--\0it won't start showing the next message until all the commands executed to display the -current message have terminated. In the case of a multipart content -(of any subtype listed above), the content contains advice indicating if -the parts should be displayed serially or in parallel. Because this may -cause confusion, particularly on uni-window displays, the -.B \-serialonly -switch can be given to tell -.B mhshow -to never display parts in parallel. +current message have terminated. .SS "Showing Alternate Character Sets" +If +.B mhshow +was built with +.IR iconv (3), +then all text/plain parts of the message(s) will be displayed using +the character set of the current locale. See the +.BR mhparam (1) +man page for how determine whether your +.B nmh +installation includes +.IR iconv (3) +support. To convert text parts other +than text/plain, or if +.B mhshow +was not built with +.IR iconv , +an external program can be used, as described next. +.PP Because a content of type text might be in a non-ASCII character set, when .B mhshow @@ -325,15 +341,15 @@ encounters a \*(lqcharset\*(rq parameter for this content, it checks if your terminal can display this character set natively. .B mhn -checks this by examining the the environment -variable -.BR $MM_CHARSET . -If the value of this environment variable is equal +checks this by examining the current character set defined by the +.IR locale (1) +environment variables. +If the value of the locale character set is equal to the value of the charset parameter, then .B mhshow assumes it can -display this content without any additional setup. If this environment -variable is not set, +display this content without any additional setup. If the locale is not +set properly, .B mhshow will assume a value of \*(lqUS-ASCII\*(rq. If the character set cannot be displayed natively, then @@ -376,29 +392,24 @@ needed beforehand. Note that many pagers strip off the high-order bit or have problems displaying text with the high-order bit set. However, the pager .B less -has support for single-octet character sets. The source -to -.B less -is available on many ftp sites carrying free software. -In order to view messages sent in the ISO-8859-1 character set using +has support for single-octet character sets. For example, messages +encoded in the ISO-8859-1 character set can be view using .BR less , -.PP -put these lines in your -.I \&.login -file: +with these environment variable settings: .PP .RS 5 .nf -setenv LESSCHARSET latin1 -setenv LESS "-f" +.ta \w'%F 'u +LESSCHARSET latin1 +LESS -f .fi .RE .PP -The first line tells +The first setting tells .B less to use the ISO-8859-1 definition for determining whether a character is \*(lqnormal\*(rq, \*(lqcontrol\*(lq, -or \*(lqbinary\*(rq. The second line tells +or \*(lqbinary\*(rq. The second setting tells .B less not to warn you if it encounters a file that has non-ASCII characters. Then, simply @@ -436,6 +447,8 @@ ftp local-file .IP \(bu 4 mail-server +.IP \(bu 4 +url .PP For the \*(lqanon-ftp\*(rq and \*(lqftp\*(rq access types, .B mhshow @@ -464,6 +477,14 @@ local filename .PP The program should terminate with an exit status of zero if the retrieval is successful, and a non-zero exit status otherwise. +.PP +For the \*(lqurl\*(rq access\-type, +.B mhshow +will look for the \*(lqnmh-access-url\*(rq +profile entry. See +.IR mhstore (1) +for more details. +.PP .SS "The Content Cache" When .B mhshow @@ -551,6 +572,15 @@ which is created automatically during .B nmh installation. .SH FILES +.B mhshow +looks for all format files and mhn.defaults in multiple locations: +absolute pathnames are accessed directly, tilde expansion is done on +usernames, and files are searched for in the user's +.I Mail +directory as specified in their profile. If not found there, the directory +.RI \*(lq %etcdir% \*(rq +is checked. +.PP .fc ^ ~ .nf .ta \w'%etcdir%/ExtraBigFileName 'u @@ -569,6 +599,7 @@ installation. ^Unseen\-Sequence:~^To name sequences denoting unseen messages ^mhlproc:~^Default program to display message headers ^nmh-access-ftp:~^Program to retrieve contents via FTP +^nmh-access-url:~^Program to retrieve contents via HTTP ^nmh-cache~^Public directory to store cached external contents ^nmh-private-cache~^Personal directory to store cached external contents ^mhshow-charset-~^Template for environment to render character sets @@ -576,9 +607,11 @@ installation. ^moreproc:~^Default program to display text/plain content .fi .SH "SEE ALSO" +.IR iconv (3), .IR mhbuild (1), .IR mhl (1), .IR mhlist (1), +.IR mhparam (1), .IR mhstore (1), .IR sendfiles (1) .SH DEFAULTS @@ -587,9 +620,7 @@ installation. .RB ` msgs "' defaults to cur" .RB ` \-nocheck ' .RB ` \-form\ mhl.headers ' -.RB ` \-pause ' .RB ` \-rcache\ ask ' -.RB ` \-noserialonly ' .RB ` \-wcache\ ask ' .fi .SH CONTEXT