From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: Book recommendation
Date: Mon, 28 Aug 2006 16:11:15 -0700 [thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICEEHFDIAA.drew.adams@oracle.com> (raw)
In-Reply-To: <878xl8345t.fsf@mail.com>
The elisp info/manual is too much like a standard. Is there a
K&R type
(ugh! ouf!)
book you
can recommend for elisp? One that takes you on a journeay with the
language while developing small programs?
Try the Emacs Lisp Introduction manual (also in Info). It is essentially a
tutorial, with lots of examples. It leads you by the hand well.
How much like "Lisp" is "elisp"? The same? is there *a* Lisp? or does it
vary a lot?
Emacs Lisp (what you called "elisp") is a Lisp. What do you mean by "a lot"?
What's your yardstick?
What would you recommend for someone to get to grips with advanced Lisp
programming in emacs?
Start with the Emacs Lisp Introduction manual. There is enough "advanced
programming" stuff in there to keep you busy for a while.
Is (debugger) the only debugger? Seems kind of antiquated and hard to
use - even gdb provides more for C debugging in emacs.
There are several debuggers for Emacs. See the Emacs Lisp manual (elisp).
--
IMO, Emacs Lisp is a *very* good Lisp to learn Lisp with. Others might
disagree (but they're of course wrong).
next prev parent reply other threads:[~2006-08-28 23:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 22:07 Book recommendation Hadron Quark
2006-08-28 22:58 ` Eric Hanchrow
2006-08-28 23:11 ` Drew Adams [this message]
[not found] ` <mailman.5862.1156806504.9609.help-gnu-emacs@gnu.org>
2006-08-29 3:13 ` Hadron Quark
2006-08-29 19:57 ` Kevin Rodgers
-- strict thread matches above, loose matches on Subject: below --
2005-07-24 12:08 book recommendation Baloff
2005-07-23 20:42 ` Drew Adams
2005-07-23 22:29 ` Alan Mackenzie
2005-07-23 23:01 ` Zephyre
2005-08-21 2:02 ` Stefan Monnier
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=DNEMKBNJBGPAOPIJOOICEEHFDIAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
/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).