From: Perry Smith <pedz@easesoftware.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Q: How did _YOU_ learn Elisp?
Date: Fri, 1 Dec 2006 10:52:18 -0600 [thread overview]
Message-ID: <816BD325-3F2A-485F-B15B-71F48013E744@easesoftware.com> (raw)
In-Reply-To: <87vekvlxeq.fsf@localhost.localdomain>
[-- Attachment #1.1: Type: text/plain, Size: 902 bytes --]
I learned over a long of time -- before there was an emacs lisp
manual. I used Guy Steel's book on Common Lisp as a basic guide to
lisp. I would not use it today though. It is nice because you have
all the source available. So, just like doing html pages is often
the process of find a page that does what you want to do and see how
they did it, elisp is the same: find something that is close,
understand how it works, then modify it.
So, basically, I would start small, do tweeks and adjustments to
existing things. Then move on to bigger things. I generally write
most of my stuff in the *scratch* buffer so I can experiment and play
quickly. There is another mode that can be used but I never learned it.
Perry Smith ( pedz@easesoftware.com )
Ease Software, Inc. ( http://www.easesoftware.com )
Low cost SATA Disk Systems for IBMs p5, pSeries, and RS/6000 AIX systems
[-- Attachment #1.2: Type: text/html, Size: 4571 bytes --]
[-- Attachment #2: Type: text/plain, Size: 152 bytes --]
_______________________________________________
help-gnu-emacs mailing list
help-gnu-emacs@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnu-emacs
next prev parent reply other threads:[~2006-12-01 16:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 10:31 Q: How did _YOU_ learn Elisp? Passer By
2006-12-01 10:42 ` Bastien
2006-12-01 10:52 ` Gian Uberto Lauri
2006-12-01 11:47 ` Florian Kaufmann
2006-12-01 13:45 ` Mirko
2006-12-01 14:54 ` Gian Uberto Lauri
2006-12-01 16:17 ` Mark T.B. Carroll
2006-12-01 16:52 ` Perry Smith [this message]
2006-12-01 17:23 ` Robert Thorpe
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=816BD325-3F2A-485F-B15B-71F48013E744@easesoftware.com \
--to=pedz@easesoftware.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).