Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!uunet!osh3!chip
From: chip@osh3.OSHA.GOV (Chip Yamasaki)
Newsgroups: comp.mail.elm
Subject: Re: Hey Syd, here's a couple of ideas!
Message-ID: <1991Jun23.044553.11687@osh3.OSHA.GOV>
Date: 23 Jun 91 04:45:53 GMT
References: <1991Jun20.044510.781@osh3.OSHA.GOV> <1991Jun20.141539.16160@DSI.COM> <1991Jun21.184912.6954@gjetor.geac.COM>
Organization: U.S. D.O.L - Occupational Safety & Health Admin.
Lines: 33

In <1991Jun21.184912.6954@gjetor.geac.COM> adeboer@gjetor.geac.COM (Anthony DeBoer) writes:

>In article <1991Jun20.141539.16160@DSI.COM> syd@DSI.COM writes:
>>chip@osh3.OSHA.GOV (Chip Yamasaki) writes:
>>>Another complaint is no binary attachments.
>>
>>This one has been under discussion since 2.2 was being developed.  We
>>even, internally, floated a proposal about it.  No one did anything
>>with it, partly because the AT&T method, Content-Type:/Content-Length:
>>for attachments didn't go anywhere and become a 'global' standard,
>>and at that time, not too much need, compared to now.  Plus, at that
>>time, most mail transports were not 8 bit clean, so the best
>>we could do would be a uuencoded attachment....

>Isn't uuencode a defacto standard?  Perhaps a way of improving its interface
>to Elm would be for the pager to recognise and skip uuencoded files on
>display, but to tag these as attachments and offer appropriate options (like
>being able to mkdir/cd to the desired place to park them, from within Elm).

Exactly what I was saying, and this is what Cymail does.

>My only really major beef with the pager in the current release is the lack
>of a page-backup key.  A line-backup would be nice too.  I tried using less
>as my pager for awhile, but losing the "d" and "j" commands made this a
>temporary thing.

Ditto.  I tried it and missed these features.  I'd love to see less
adapted to work smoothly with Elm.
-- 
-----------------------+---------------------------------------------------
Charles "Chip" Yamasaki| The opinions expressed here are my own and are not
chip@oshcomm.osha.gov  | supported or even generally accepted by OSHA. :-)
-----------------------+---------------------------------------------------