Debian Codegraph @

samples/mailcap

raw
1 # Copyright (c) 1991 Bell Communications Research, Inc. (Bellcore)
2 #
3 # Permission to use, copy, modify, and distribute this material
4 # for any purpose and without fee is hereby granted, provided
5 # that the above copyright notice and this permission notice
6 # appear in all copies, and that the name of Bellcore not be
7 # used in advertising or publicity pertaining to this
8 # material without the specific, prior written permission
9 # of an authorized representative of Bellcore. BELLCORE
10 # MAKES NO REPRESENTATIONS ABOUT THE ACCURACY OR SUITABILITY
11 # OF THIS MATERIAL FOR ANY PURPOSE. IT IS PROVIDED "AS IS",
12 # WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES.
13 #
14 # Prototype Mailcap file
15 # Note that support for text & multipart are "built in" to metamail,
16 # as are rudimentary support for message, and application.
17 # However, any of these may be overridden in mailcap.
18 #
19 # Note that users may override or extend this with a .mailcap
20 # file in their own directory. However, there is NO NEED
21 # for them to copy entries from this file, as metamail will
22 # pick up entries from both the system and personal mailcap files.
23 #
24
25 # NOTE: This file has been heavily modified for use as an example
26 # configuration file for Lynx
27
28 # In the samples given test=test -n "$DISPLAY" is used to
29 # determine if the current session is X capable by checking
30 # for the existence of a DISPLAY environment variable.
31 # Lynx actually uses a getenv() call for DISPLAY (DECW$DISPLAY
32 # on VMS) when it encounters test=test -n "$DISPLAY" or
33 # test=test -z "$DISPLAY" in a viewer assignment, instead of
34 # spawning to execute "test" via a system() call, i.e., those
35 # two strings, respectively, are handled equivalently to the
36 # :XWINDOWS and :NON_XWINDOWS flags for VIEWER: assignments
37 # in lynx.cfg. Any system without the DISPLAY (or DECW$DISPLAY)
38 # environment variable will be assumed to be Non-X.
39
40 # You can append a ';' followed by "q=#.#", e.g., ; q=0.002
41 # to set the quality parameter for the Content-Type, which can be
42 # included in the Accept: header Lynx sends to http servers (the
43 # default quality value is 1.0, and Lynx appends the parameter
44 # to the Content-Type only if the value is less than 1.0).
45
46 # You can append a ';' followed by "mxb=#", e.g., ; mxb=1000000
47 # to set the maxbytes parameter for the Content-Type, which can be
48 # included in the Accept: header Lynx sends to http servers (the
49 # default maxbytes value is 0, meaning no maximum, and Lynx appends
50 # the parameter to the Content-Type only if the value exceeds 0).
51
52 # The following line is for sites where xv understands jpeg but xloadimage
53 # is preferred.
54 #
55 # the test line specifies that this viewer should only be used if
56 # the display variable is set.
57 image/jpeg; xv %s; test=test -n "$DISPLAY"
58
59 # The following sends all other image subtypes to xloadimage
60 #image/*; xloadimage %s; ; test=test -n "$DISPLAY"
61
62 # The following sends all other image subtypes to xv
63 image/*; xv %s; ; test=test -n "$DISPLAY"
64
65
66 # If you have an interactive Postscript interpreter, you should think carefully
67 # before replacing lpr with it in the following line, because PostScript
68 # can be an enormous security hole. It is RELATIVELY harmless
69 # when sent to the printer...
70
71 # This one is for NON-X
72 #application/postscript; lpr %s \; echo SENT FILE TO PRINTER; ;test=test -z "$DISPLAY"
73
74 # This one is for X. It's already the default via src/HTInit.c.
75 #application/postscript; ghostview %s; ; test=test -n "$DISPLAY"
76
77 # The following should be commented out if you do NOT have safe-tcl
78 # and should be uncommented if you DO have safe-tcl
79 #application/safe-tcl; swish -safe -messaging -f %s
80
81 # A common problem with the mailcap mechanism is getting differential
82 # behavior from different programs. This problem is compounded by the fact
83 # that some programs, notably Mosaic, do not implement the "test" clause in
84 # mailcap files. If you are using Lynx and X Mosaic together you should
85 # place all X-centric entries before non-X entries. X Mosaic will use
86 # whichever entry is defined first so further entries will be ignored.
87 #
88 # Lynx exports the environment variable LYNX_VERSION, so it can be tested
89 # by scripts to determine if Lynx is running or not. However, the string
90 # test=test -n "$LYNX_VERSION"
91 # is handled simply as a flag which yields success when Lynx encounters it
92 # in the mailcap file (i.e., Lynx does not bother to execute "test" via a
93 # system() call to find out if it's running, because it obviously is).
94 # Inclusion of the string for that test can be used to prevent other
95 # software which reads the mailcap file from acting on assignments intended
96 # only for Lynx. The string
97 # test=test -z "$LYNX_VERSION"
98 # similarly is treated by Lynx simply as a flag which yields failure.
99