On Thu, Oct 21, 1999 at 01:20:33AM -0400, Tim Pierce thus spoke:
> On Sat, Oct 16, 1999 at 12:59:00AM +0200, [EMAIL PROTECTED] wrote:
> > On Sat, Oct 09, 1999 at 12:05:51AM +0000, Shao Zhang wrote:
> > > Sorry, a bit off topic, but just wondering...
> > >
> > > So why mutt implements a pop3 protocol? Why do we need this when we have
> > > fetchmail?
> > >
> >
> > ...and why have a pager while we have more and less.
>
> Heck, at this rate, why should mutt implement mail when we have /usr/bin/mail?
Well geez...carrier pigeon with quill and parchment worked just fine...why
did we impliment computers and electronic communication? Actually, until a
few years ago (maybe 3), carrier pigeon would have been faster to
Australia. :) It still is to some points routed through
west-orange.cw.net. :(
Anyway, that's getting to be a bit extreme...questioning the pager. The
pager is implimented so that it can do some nice things like colouring,
etc. It's an enhancement specifically meant to deal with email reading.
I guess the fine line deals with whether something needs to deal with a
protocol or not, and whether said protocol should be in an MUA. Since a
protocol isn't involved in a pager, it doesn't get to stage 2 of the
question. At least that's how I see the decision-making process re: mutt.
mark->
--
Fairlight-> ||| [EMAIL PROTECTED] | Fairlight Consulting
__/\__ ||| "I'm talking for free... | http://www.fairlite.com
<__<>__> ||| It's a New Religion..." | [EMAIL PROTECTED]
\/ ||| PGP Public Key available via finger @iglou, or Key servers
