From xemacs-m  Sat Mar  1 18:01:29 1997
Received: from crystal.WonderWorks.COM (crystal.WonderWorks.com [192.203.206.1])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id SAA22455
	for <xemacs-beta@xemacs.org>; Sat, 1 Mar 1997 18:01:27 -0600 (CST)
Received: by crystal.WonderWorks.COM 
	id QQcfbc20417; Sat, 1 Mar 1997 19:01:27 -0500 (EST)
Date: Sat, 1 Mar 1997 19:01:27 -0500 (EST)
Message-Id: <QQcfbc20417.199703020001@crystal.WonderWorks.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Kyle Jones <kyle_jones@wonderworks.com>
To: xemacs-beta@xemacs.org
Subject: VM things
In-Reply-To: <199703012324.QAA15154@branagh.ta52.lanl.gov>
References: <199703012324.QAA15154@branagh.ta52.lanl.gov>
X-Face: /cA45WHG7jWq>(O3&Z57Y<"WsX5ddc,4c#w0F*zrV#=M
        0@~@,s;b,aMtR5Sqs"+nU.z^CSFQ9t`z2>W,S,]:[+2^
        Nbf6v4g>!&,7R4Ot4Wg{&tm=WX7P["9%a)_da48-^tGy
        ,qz]Z,Zz\{E.,]'EO+F)@$KtF&V

John A. Turner writes:
 > 19.15b95, VM 6.15, Gnus 5.4.15
 > Motif dialogs, Lucid scrollbars & menus
 > Solaris 2.5.1, CDE 1.0.2, focus-follows-mouse
 > 
 > ----
 > 
 > Several things related to VM:
 > 
 > o Anyone else seeing weirdness when trying to scroll after doing
 >   mouse-2 to view an image?  Scrollbars are extremely sensitive after
 >   the image is expanded (e.g. a gif displayed internally).

Scrolling has always worked this way in the face of large images.

 >   Kyle, at one point you mentioned maybe just turning off s-i-p in VM
 >   altogether.  Why not, since it causes such havoc?

I intended to, but I missed a spot in the code.

 > [...]
 > plain text, X-CTEXT                 [Click mouse-2 to display]
 > 
 >   At this point, I know I could have hit D again to expand it, but I
 >   decided to try mouse-2 to see what would happen.  But when I did, it
 >   prompted for a filename.
 > 
 >   Not a big deal; I just hit D and read the thing, but the point is
 >   that mouse-2 didn't do what it said it would.

The code that produces the buttons can't really know if a later
display action is going to succeed.  x-ctext is an unknown
character set so displaying the message internally failed.  The
fallback action is to save it to a file.

 > o I have ("application/x-dvi" "xdvi") in my
 >   vm-mime-external-content-types-alist, but when I mailed myself a
 >   .dvi file it showed up with
 > 
 > manual.dvi                          [Click mouse-2 to save to a file]
 > 
 >   in the body of the msg.  A single D didn't seem to do anything, and
 >   a 2nd expanded the whole mess, but why didn't it say [Click mouse-2
 >   to display] and then use xdvi to display?

The type in the message and the type in the alist must not have
matched.

 > o Another thing related to that last one.  When I tried to attach that
 >   .dvi it tried to add it as an application/octet-stream and I had to 
 >   manually tell it application/x-dvi.  Shouldn't it have known from
 >   the .dvi suffix?
 > 
 >   Oops.  Nevermind.  Just found vm-mime-attachment-auto-type-alist.
 >   Think it might be common enough be added to the default in
 >   vm-vars.el? 

x-foo types are non-standard.  I don't want to add any of these
as defaults.  People should get off their keisters and register
the MIME types they want to use.

