version 1, including all changes.
.
Rev |
Author |
# |
Line |
1 |
perry |
1 |
MAILCAP.ORDER |
|
|
2 |
!!!MAILCAP.ORDER |
|
|
3 |
NAME |
|
|
4 |
DESCRIPTION |
|
|
5 |
LIMITATIONS |
|
|
6 |
AUTHOR |
|
|
7 |
---- |
|
|
8 |
!!NAME |
|
|
9 |
|
|
|
10 |
|
|
|
11 |
/etc/mailcap.order - the mailcap ordering specifications |
|
|
12 |
!!DESCRIPTION |
|
|
13 |
|
|
|
14 |
|
|
|
15 |
The order of entries in the ''/etc/mailcap'' file can be |
|
|
16 |
altered by editing the ''/etc/mailcap.order'' file. Each |
|
|
17 |
line of that file specifies a package and an optional mime |
|
|
18 |
type. Mailcap entries that match will be placed in the order |
|
|
19 |
of this file. Entries that don't match will be placed |
|
|
20 |
later. |
|
|
21 |
|
|
|
22 |
|
|
|
23 |
__Example__ |
|
|
24 |
|
|
|
25 |
|
|
|
26 |
mime-support:*/* gv:application/postscript |
|
|
27 |
netscape:text/html less:text/* emacs:text/* |
|
|
28 |
|
|
|
29 |
|
|
|
30 |
The above would make any entries provided by the |
|
|
31 |
__mime-support__ package (as found in the |
|
|
32 |
''/usr/lib/mime/packages'' directory) take priority over |
|
|
33 |
everything else. The __gv__ package will be used over |
|
|
34 |
anything else when it comes to postscript documents. |
|
|
35 |
__Netscape__ will be used for any html documents and |
|
|
36 |
__less__ will be used for any remaining text documents. |
|
|
37 |
However, since neither netscape or less provide for editing |
|
|
38 |
documents, any edit or compose actions will fall through to |
|
|
39 |
the __emacs__ rules. |
|
|
40 |
|
|
|
41 |
|
|
|
42 |
After modifying this file, be sure to run |
|
|
43 |
''/usr/sbin/update-mime'' (as root) to propagate the |
|
|
44 |
changes into the ''/etc/mailcap'' file. |
|
|
45 |
!!LIMITATIONS |
|
|
46 |
|
|
|
47 |
|
|
|
48 |
There is currently no way to break out a certain type from a |
|
|
49 |
wildcard rule. If, for example, both xv and gimp were to |
|
|
50 |
specify |
|
|
51 |
gif'' images but use gimp for ''jpeg'' |
|
|
52 |
images. |
|
|
53 |
|
|
|
54 |
|
|
|
55 |
Also, I would like to add the ability to specify certain |
|
|
56 |
actions in the rules. For example, if netscape were to have |
|
|
57 |
an ''edit'' rule but I wanted to use emacs for |
|
|
58 |
editing/creating html documents, I could place a line |
|
|
59 |
like |
|
|
60 |
|
|
|
61 |
|
|
|
62 |
emacs:text/* action=edit|compose |
|
|
63 |
|
|
|
64 |
|
|
|
65 |
before the netscape entry. The __update-mime__ program |
|
|
66 |
would then spit out entries such that netscape ''view'' |
|
|
67 |
rule comes __before__ the emacs ''view'' rule but have |
|
|
68 |
the netscape ''edit'' rule comes __after__ the emacs |
|
|
69 |
''edit'' rule. |
|
|
70 |
!!AUTHOR |
|
|
71 |
|
|
|
72 |
|
|
|
73 |
The __mailcap.order__ specification was written by Brian |
|
|
74 |
White __ |
|
|
75 |
---- |