From: David Moore <dmoore@UCSD.EDU>
Subject: Re: Acronym lookups
Date: 09 Jan 1997 09:17:11 -0800 [thread overview]
Message-ID: <rvenfuahuw.fsf@sdnp5.ucsd.edu> (raw)
In-Reply-To: Wesley.Hardaker@sphys.unil.ch's message of 09 Jan 1997 17:38:11 +0100
Wesley.Hardaker@sphys.unil.ch 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...
I tend to agree with Per here. The functionality seems useful
outside of Gnus (such as many reports and C code you have to read/edit
that might have acronyms in them). Otherwise shouldn't ispell.el and
webster.el be included with Gnus too? All good news readers prevent you
from making spelling mistakes. :)
--
David Moore <dmoore@ucsd.edu> | Computer Systems Lab __o
UCSD Dept. Computer Science - 0114 | Work: (619) 534-8604 _ \<,_
La Jolla, CA 92093-0114 | Fax: (619) 534-1445 (_)/ (_)
<URL:http://oj.egbt.org/dmoore/> |
next prev parent reply other threads:[~1997-01-09 17:17 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 [this message]
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
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=rvenfuahuw.fsf@sdnp5.ucsd.edu \
--to=dmoore@ucsd.edu \
/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).