From: Wesley.Hardaker@sphys.unil.ch
Subject: Re: Acronym lookups
Date: 10 Jan 1997 10:01:33 +0100 [thread overview]
Message-ID: <qk2g209x5si.fsf@iptsun2.unil.ch> (raw)
In-Reply-To: "William M. Perry"'s message of Thu, 9 Jan 1997 11:28:36 -0800
>>>>> "William" == William M Perry <wmperry@aventail.com> writes:
William> This has been bothering me a bit lately. Lars (GNUS), Kyle
William> (VM), and I (W3) seem to be reimplementing a lot of the same
William> functionality. Notably base64 decoding, md5, POP
William> functionality, rot13, etc, etc.
Well, I do agree with this of course! Heck, thats one of the reasons
that oo is so popular with the theoretical crowd, its supposed to
support this type of re-use.
The reason I figured I'd just submit it here was that it would get
included with both Emacs and XEmacs since they both follow gnus.
XEmacs keeps track of a bunch of packages, but Emacs doesn't and gnus
is but one of a minor few so I thought if it was going to add a key
binding for it it should be shipped with it... Then if something like
VM or W3 wants to add a keybinding as well, thats no problem as just
because its in the gnus sub-dir in the load path, it can still find
it... Gnus is shipped with both packages?
Make Sense? I thought not... Doesn't to me much either...
Wes
next prev parent reply other threads:[~1997-01-10 9:01 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
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 [this message]
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=qk2g209x5si.fsf@iptsun2.unil.ch \
--to=wesley.hardaker@sphys.unil.ch \
/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).