From: "William M. Perry" <wmperry@aventail.com>
Cc: ding@ifi.uio.no
Subject: Re: Acronym lookups
Date: Thu, 9 Jan 1997 11:28:36 -0800 [thread overview]
Message-ID: <199701091928.LAA10033@newman> (raw)
In-Reply-To: <qk2zpyi3ito.fsf@iptsun2.unil.ch>
Wesley Hardaker writes:
>>>>>> "Per" == Per Abrahamsen <abraham@dina.kvl.dk> writes:
>
>Per> I don't see it has anything to do with news, it should be a separate
>Per> package like webster.el, and posted to gnu.emacs.sources.
>
>Well, I'm not sure I totally agree... Granted, it should probably be
>posted there as well, but... Shouldn't all good news readers (ie,
>pretty much just gnus) be able to help you decypher the articles you
>are reading, and hence be able to look up acronyms? I mean, you have
>rot13 built in to decode articles, what about acronym-lookup...
>
>Feeling in sort of a devils advocate kinda mood... sorry...
This has been bothering me a bit lately. Lars (GNUS), Kyle (VM), and I
(W3) seem to be reimplementing a lot of the same functionality. Notably
base64 decoding, md5, POP functionality, rot13, etc, etc.
_ALL_ of this functionality should be available to other applications
easily, without requiring the user to load up all of GNUS/VM/W3 to be able
to base64 a !%#*ing file. This is one of the reasons I've been slowly
rewriting chunks of W3 to be more modular. VM, GNUS, and W3 can all
benefit from a standard set of libraries that do:
- Mailcap Parsing
- base64 (en|de)coder
- Quoted printable (en|de)code
- rot13 display code
- URL loading
- RFC822 header parsing
Any others?
Can't we all just get along? :) I'd love to see VM use a user's mailcap
file now that it has MIME suppport, GNUS too. Well, enough of this tirade,
I'll send mail to lars and kyle privately to discuss some of this, and
hope.
As you can guess, I'd say distribute it separately, and do your best not
to require stuff you don't absolutely need from GNUS, to make it easier for
people to using it elsewhere.
-Bill P.
next prev parent reply other threads:[~1997-01-09 19:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-01-08 13:48 Wesley.Hardaker
1997-01-09 11:03 ` Lars Magne Ingebrigtsen
1997-01-09 11:29 ` Per Abrahamsen
1997-01-09 16:38 ` Wesley.Hardaker
1997-01-09 17:17 ` David Moore
1997-01-09 19:28 ` William M. Perry [this message]
1997-01-09 20:38 ` Steinar Bang
1997-01-09 20:49 ` Lars Magne Ingebrigtsen
1997-01-09 23:31 ` William M. Perry
1997-01-09 23:35 ` Steven L Baur
1997-01-10 0:15 ` Sudish Joseph
1997-01-10 8:03 ` Steinar Bang
1997-01-09 21:51 ` Karl Kleinpaste
1997-01-10 9:01 ` Wesley.Hardaker
1997-01-09 12:49 ` Lars Balker Rasmussen
1997-01-09 16:35 ` Wesley.Hardaker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199701091928.LAA10033@newman \
--to=wmperry@aventail.com \
--cc=ding@ifi.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).