Subject: Re: display Application/POSTSCRIPT

From: [email-masked] (Timothy P. Cheney)
Date: 9 Dec 1996 17:08:10 GMT

Yvan Guillemain ([email-masked]) wrote:
: Hello,
: Is it possible to set some configuration in pine which enable me to
: display a "Application/POSTSCRIPT" attachement with a chosen command
: (PS viewer)

: \yvan

Use .mailcap in your home directory for your personal configurations and /etc/mailcap
for system-wide config.

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
|  [email-masked]                                |
|  Timothy P. Cheney              (215) 898-3197        |
|  Population Studies Center                            |
|  219 McNeil/6298                                      |
|  University of Pennsylvania                           |
|  Philadelphia, PA 19104                               |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

---

From: Fyodor Yarochkin <[email-masked]>
Date: Thu, 12 Dec 1996 17:52:32 +0600 (GMT+0500)

> Use .mailcap in your home directory for your personal configurations and /etc/mailcap
hey.. I just searched MailCap file in my sistem and didn't find it, and i 
didn't find any .mailcap files in my home directory as well, is there
 any other config files?
 just wonder?

 fyodor

---

From: Fyodor Yarochkin <[email-masked]>
Date: Thu, 12 Dec 1996 17:52:32 +0600 (GMT+0500)

fyodor

---

From: [email-masked]
Date: Thu, 12 Dec 1996 14:47:03 +0100 (MET)

On Thu, 12 Dec 1996, Fyodor Yarochkin wrote:

-> > 
-> > Use .mailcap in your home directory for your personal configurations and /etc/mailcap
-> > for system-wide config.
-> hey.. I just searched MailCap file in my sistem and didn't find it, and i 
-> didn't find any .mailcap files in my home directory as well, is there
->  any other config files?
->  just wonder?
-> 
-> 
->  fyodor
-> 
I found the wanted file as <pine-builddir>/doc/mailcap.unx

-----------------------------------------------------------------------
Rudolf Kompf                     | E-mail: [email-masked]

---

From: Mark Wilcutts <[email-masked]>
Date: Tue, 10 Dec 1996 21:31:06 -0800

IF you are using Unix pine, you need to set up .mailcap and .mime.types
files in your home directory. I have attached mine for reference. 
I have set up dxpsview as my viewer, yours will probably be something
else.

Good luck

--
Mark Wilcutts

On Mon, 9 Dec 1996, Yvan Guillemain wrote:

> Hello,
> Is it possible to set some configuration in pine which enable me to
> display a "Application/POSTSCRIPT" attachement with a chosen command
> (PS viewer)

# example mime.types file.
# see the NCSA X Mosaic documentation at
# http://www.ncsa.uiuc.edu/SDG/Software/Mosaic/Docs/extension-map.html
# for more details

application/postscript         ai eps ps
application/rtf                rtf
application/x-tex              tex
application/x-texinfo          texinfo texi
application/x-troff            t tr roff
audio/basic                    au snd
audio/x-aiff                   aif aiff aifc
audio/x-wav                    wav
image/gif                      gif
image/ief                      ief
image/jpeg                     jpeg jpg jpe
image/tiff                     tiff tif
image/x-xwindowdump            xwd
text/html                      html
text/plain                     txt c cc h
video/mpeg                     mpeg mpg mpe
video/quicktime                qt mov
video/x-msvideo                avi
video/x-sgi-movie              movie

# Copyright (c) 1991 Bell Communications Research, Inc. (Bellcore)
#
# Permission to use, copy, modify, and distribute this material
# for any purpose and without fee is hereby granted, provided
# that the above copyright notice and this permission notice
# appear in all copies, and that the name of Bellcore not be
# used in advertising or publicity pertaining to this
# material without the specific, prior written permission
# of an authorized representative of Bellcore.  BELLCORE
# MAKES NO REPRESENTATIONS ABOUT THE ACCURACY OR SUITABILITY
# OF THIS MATERIAL FOR ANY PURPOSE.  IT IS PROVIDED "AS IS",
# WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES.
#
# Prototype Mailcap file
# Note that support for text & multipart are "built in" to metamail,
# as are rudimentary support for message, and application.
# However, any of these may be overridden in mailcap.
#
# Note that users may override or extend this with a .mailcap
# file in their own directory.  However, there is NO NEED
# for them to copy entries from this file, as metamail will
# pick up entries from both the system and personal mailcap files.
#

# NOTE:  This file has been heavily modified for use as an example
#        configuration file for Lynx

# In the samples given   test=test -n "$DISPLAY"   is used to
# determine if the current session is X capible by checking
# for the existance of a DISPLAY environment variable.
# Lynx actually uses a getenv() call for DISPLAY (DECW$DISPLAY
# on VMS) when it encounters   test=test -n "$DISPLAY"  or
# test=test -z "$DISPAY"  in a viewer assignment, instead of
# spawning to execute "test" via a system() call, i.e., those
# two strings, respectively, are handled equivalently to the
# :XWINDOWS and :NON_XWINDOWS flags for VIEWER: assignments
# in lynx.cfg.  Any system without the DISPLAY (or DECW$DISPLAY)
# environment variable will be assumed to be Non-X.

# The following line is for sites where xv understands jpeg but xloadimage
# is preferred.
#
# the test line specifies that this viewer should only be used if
# the display variable is set.
image/jpeg; xv %s;  test=test -n "$DISPLAY"

# The following sends all other image subtypes to xloadimage
#image/*; xloadimage %s; ;  test=test -n "$DISPLAY"

# The following sends all other image subtypes to xv
image/*; xv %s; ;  test=test -n "$DISPLAY"

# If you have an interactive Postscript interpreter, you should think carefully

# before replacing lpr with it in the following line, because PostScript
# can be an enormous security hole.  It is RELATIVELY harmless
# when sent to the printer...

# This one is for NON-X
#application/postscript ; lpr %s \; echo SENT FILE TO PRINTER; ;test=test -z "$DISPLAY"

# This one is for X.  It's already the default via src/HTInit.c.
#application/postscript ; ghostview %s; ;  test=test -n "$DISPLAY"
application/postscript ; dxpsview %s; ;  test=test -n "$DISPLAY"

# The following should be commented out if you do NOT have safe-tcl
# and should be uncommented if you DO have safe-tcl
#application/safe-tcl; swish -safe -messaging -f %s

audio/basic; decsound -f %s

# A common problem with the mailcap mechanism is getting differential
# behavior from different programs.  This problem is compounded by the fact
# that some programs, notably Mosaic, do not implement the "test" clause in
# mailcap files.  If you are using Lynx and X Mosaic together you should
# place all X-centric entries before non-X entries.  X Mosaic will use
# whichever entry is defined first so further entries will be ignored.
#
# On Unix, Lynx exports the environment variable LYNX_VERSION, so it can
# be tested by scripts to determine if Lynx is running or not.  However,
# for both Unix and VMS, the string  test=test -n "$LYNX_VERSION"   is
# handled simply as a flag which yields success when Lynx encounters it
# in the mailcap file (i.e., Lynx does not bother to execute "test" via
# a system() call to find out if it's running, because it obviously is).
# Inclusion of the string for that test can be used to prevent other
# software which reads the mailcap file from acting on assignments
# intended only for Lynx.  The string  test=test -z "$LYNX_VERSION"
# similarly is treated by Lynx simply as a flag which yields failure.