From: Dan Anderson <dan@mathjunkies.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Is it better to use eLISP or Common LISP?
Date: Tue, 21 Oct 2003 10:36:19 -0400 [thread overview]
Message-ID: <1066746978.4475.40.camel@syr-24-59-77-252.twcny.rr.com> (raw)
In-Reply-To: <vfoewaj18o.fsf@rpc71.cs.man.ac.uk>
> >> I know that I can either use Emacs LISP or the eLISP file that
> >> interfaces with common LISP.
>
> I don't know what this means. What "elisp file that interfaces with
> common lisp". If you want emacs to do things, then you can use emacs
> lisp, or emacs lisp.
I think I found an emacs lisp file that allows you to extend emacs using
common lisp. Perhaps I was reading the manifest wrong.
-Dan
next prev parent reply other threads:[~2003-10-21 14:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-20 18:22 Is it better to use eLISP or Common LISP? Dan Anderson
2003-10-20 20:37 ` Sam Steingold
[not found] ` <mailman.2029.1066682270.21628.help-gnu-emacs@gnu.org>
2003-10-21 11:09 ` Phillip Lord
2003-10-21 14:36 ` Dan Anderson [this message]
[not found] ` <mailman.2070.1066747062.21628.help-gnu-emacs@gnu.org>
2003-10-21 14:53 ` Phillip Lord
2003-10-22 8:23 ` Tim X
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1066746978.4475.40.camel@syr-24-59-77-252.twcny.rr.com \
--to=dan@mathjunkies.com \
--cc=help-gnu-emacs@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).