unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: dkcombs@panix.com (David Combs)
To: help-gnu-emacs@gnu.org
Subject: Re: Running a lisp script
Date: Sun, 22 Apr 2012 06:06:31 +0000 (UTC)	[thread overview]
Message-ID: <jn0757$jk5$1@reader1.panix.com> (raw)
In-Reply-To: 8762dxw4l6.fsf@kuiper.lan.informatimago.com

In article <8762dxw4l6.fsf@kuiper.lan.informatimago.com>,
Pascal J. Bourguignon <pjb@informatimago.com> wrote:
>
>That said, emacs lisp is close enough to Common Lisp.  Learning Common
>Lisp, you'll know enough to write emacs lisp code.  (Mostly, emacs lisp
>is a subset of Common Lisp; there's also (require 'cl) to provide more
>CL-like operators).  ...
>
>
>
>-- 
>__Pascal Bourguignon__                     http://www.informatimago.com/
>A bad day in () is better than a good day in {}.


Outta say something about those new scoping rules that Sussman and IforgetWho
invented 30 or more years ago and created Scheme to use it with, and that
later, when Common Lisp was being decided etc, put it there too.

Too late at night for me to remember the name of the "scheme", but
Perl added it via its (sic) "local" variables.   AH -- dynamic binding,
that's what it's called.  Which Elisp doesn't have, being derived from
MacLisp thinking.

That was a long time ago.  Is what I remember actually a correct memory?

Thanks,

David




       reply	other threads:[~2012-04-22  6:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0Ixar.31221$M%7.9998@newsfe10.iad>
     [not found] ` <87obrpckkm.fsf@notengoamigos.org>
     [not found]   ` <JXyar.20747$pc1.8169@newsfe11.iad>
     [not found]     ` <8762dxw4l6.fsf@kuiper.lan.informatimago.com>
2012-04-22  6:06       ` David Combs [this message]
2012-04-22 14:01         ` Running a lisp script Juanma Barranquero
2012-04-22 19:26           ` PJ Weisberg
     [not found]           ` <mailman.444.1335122807.751.help-gnu-emacs@gnu.org>
2012-05-14  1:51             ` David Combs

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='jn0757$jk5$1@reader1.panix.com' \
    --to=dkcombs@panix.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).