From: Edward Dodge <someone@somewhere.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Writing an interactive function to accept a string argument, then call a Python script?
Date: Wed, 14 Feb 2007 10:32:52 -0700 [thread overview]
Message-ID: <m2y7n0lk57.fsf@Mac-Mini.local> (raw)
In-Reply-To: 1171365681.355908.131220@k78g2000cwa.googlegroups.com
> Meanwhile, since you're into lisp, I have a question for you: Would
> there be any real advantage to my learning it, aside from
> customizing Emacs beyond the things that other people have done that
> I can find on the Web? My impression is that the answer is no.
I can't speak for Mr. Rodgers, but I just started learning Lisp in
earnest these past couple of months. And I find the study
fascinating, and useful. Of course it helps that I use a CAD program
at work with a Lisp dialect as its extension language. Without this
excuse to learn Lisp, I'm not sure I be so studious, even though I
also happen to be a die-hard Emacs-user.
If you want to hear some interesting stories about how cool Lisp is
and how useful it can be, I recommend a sampling of the entries at
this site:
http://wiki.alu.org/The_Road_to_Lisp_Survey
Some of these stories helped me on my current path to learning Lisp by
helping me to understand that it's okay to learn Lisp. True, it's not
the acclaimed Language Du Jour, but it can still be an important and
powerful skill in your programming/computing experience. If you want
to see a good example of that in a man who is both a writer and a
programmer, check out this blog:
http://www.paulgraham.com/index.html
> I'm really just a writer who stumbled into scripting by accident,
> during a few years when I was documenting software as a technical
> writer. I enjoy fiddling with code mostly to automate various things
> I do with text processing. Python has been perfect for this purpose
> - easy to learn, easy to put down and then pick up again every few
> months as needed. I once thought about learning lisp - in fact I
> went so far as to buy "The Little Schemer" - but in the end I
> decided I could no more afford to take the time to learn it than I
> could continue to learn C, which I once dabbled in briefly for fun.
I tried "The Little Lisper" and found it helped clear up the concept
of recursion. But what is really helping me stay focussed on learning
the language as a practical matter is a book that is aptly titled
"Practical Common Lisp" by Peter Seibel. The full text of the book is
available for free online:
http://www.gigamonkeys.com/book/
I bought the dead-tree edition for reading and study away from the
computer.
--
Edward Dodge
prev parent reply other threads:[~2007-02-14 17:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 13:08 Writing an interactive function to accept a string argument, then call a Python script? Endless Story
2007-02-09 14:18 ` Stack
2007-02-10 8:49 ` Kevin Rodgers
[not found] ` <mailman.4285.1171097378.2155.help-gnu-emacs@gnu.org>
2007-02-10 10:57 ` Endless Story
2007-02-13 6:20 ` Kevin Rodgers
[not found] ` <mailman.4406.1171347657.2155.help-gnu-emacs@gnu.org>
2007-02-13 11:21 ` Endless Story
2007-02-14 17:32 ` Edward Dodge [this message]
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=m2y7n0lk57.fsf@Mac-Mini.local \
--to=someone@somewhere.org \
--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).