From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: Acronym expansion caveats
Date: 15 Jan 1997 02:10:20 +0100 [thread overview]
Message-ID: <m2915vzqtf.fsf@proletcult.slip.ifi.uio.no> (raw)
In-Reply-To: elf@ee.ryerson.ca's message of Tue, 14 Jan 1997 12:37:13 -0500
elf@ee.ryerson.ca (luis fernandes) writes:
> I've not been following the AE thread but I had some thoughts on the
> matter last night (excuse me if this has already been discussed).
>
> (One assumption I have made is that there is a function that expands
> all the acronyms in a buffer).
I don't think anybody has suggested that -- the ae things are meant
for interactive usage only, since it takes a while to get a response
from the web server for each acronym.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@ifi.uio.no * Lars Ingebrigtsen
prev parent reply other threads:[~1997-01-15 1:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-01-14 17:37 luis fernandes
1997-01-15 1:10 ` Lars Magne Ingebrigtsen [this message]
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=m2915vzqtf.fsf@proletcult.slip.ifi.uio.no \
--to=larsi@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).