unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Phillip Lord <p.lord@russet.org.uk>
Subject: Re: Is it better to use eLISP or Common LISP?
Date: 21 Oct 2003 15:53:04 +0100	[thread overview]
Message-ID: <vf7k2yiqwf.fsf@rpc71.cs.man.ac.uk> (raw)
In-Reply-To: mailman.2070.1066747062.21628.help-gnu-emacs@gnu.org

>>>>> "Dan" == Dan Anderson <dan@mathjunkies.com> writes:

  >> >> 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.

  Dan> I think I found an emacs lisp file that allows you to extend
  Dan> emacs using common lisp.  Perhaps I was reading the manifest
  Dan> wrong.


There is the "CL" packages within Emacs. This is written in Emacs
Lisp, but provides a set of functions which are found in Common Lisp
as well. 

If you want to use the CL packages, then there is no problem with
this. Many people do use these packages. But they are an
implementation of some of CL. They are not CL. If you read a book on
CL, and then try is on Emacs, even using the CL code, its not going to
work. 

Likewise you can look at EIEIO, which is Eric Ludlum's implementation
of a CLOS-u-like object system for emacs lisp. But its not CLOS.

If you want to write Emacs lisp add on's, then its Emacs Lisp you
should learn. I would suggest that you start off with this...

http://www.gnu.org/manual/emacs-lisp-intro/emacs-lisp-intro.html

If you get the .info files, you can read it as hypertext within Emacs,
and it has the advantage that the example source code in the book, is
actually directly runnable within Emacs. It's a good
introduction. Next I'd start to read the Emacs Lisp Manual. Its a bit
heavier weight, and you want to be familiar with Emacs Lisp, and Emacs
usage before you read it. The CL stuff is good to read, at about the
same time, as there are lots of useful utility functions. 

Phil

  parent reply	other threads:[~2003-10-21 14:53 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
     [not found]     ` <mailman.2070.1066747062.21628.help-gnu-emacs@gnu.org>
2003-10-21 14:53       ` Phillip Lord [this message]
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=vf7k2yiqwf.fsf@rpc71.cs.man.ac.uk \
    --to=p.lord@russet.org.uk \
    /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).