From: Rusi <rustompmody@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Real-life examples of lexical binding in Emacs Lisp
Date: Sat, 30 May 2015 09:32:32 -0700 (PDT) [thread overview]
Message-ID: <4c247f74-529f-41e4-9712-221560ff7c6c@googlegroups.com> (raw)
In-Reply-To: <87y4k6rr2i.fsf@debian.uxu>
On Saturday, May 30, 2015 at 9:27:25 PM UTC+5:30, Emanuel Berg wrote:
> Contrary to this situation, Lisp is right in front of
> us. There is no modelling in the world that will
> enhance our understanding of Lisp more than we write,
> say, 50 lines of it every day. And, doing that, one
> might actually do something useful while at it!
Some very eminent Lispers perceive Lisp rather differently:
| Lisp... McCarthy did as a theoretical exercise-- an effort to define a more | convenient alternative to the Turing Machine. Lisp was not really designed to | be a programming language
From http://www.paulgraham.com/icad.html
next prev parent reply other threads:[~2015-05-30 16:32 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3883.1432888152.904.help-gnu-emacs@gnu.org>
2015-05-29 9:30 ` Real-life examples of lexical binding in Emacs Lisp Joost Kremers
2015-05-29 11:12 ` Andreas Röhler
2015-05-29 12:13 ` Dmitry Gutov
2015-05-29 16:21 ` Phillip Lord
2015-05-29 16:50 ` Yuri Khan
2015-05-29 12:28 ` Pascal J. Bourguignon
2015-05-29 17:16 ` Andreas Röhler
2015-05-29 18:43 ` Emanuel Berg
2015-05-30 5:49 ` Rusi
2015-05-30 12:50 ` Pascal J. Bourguignon
2015-05-30 15:23 ` Rusi
2015-05-30 15:50 ` Pascal J. Bourguignon
2015-05-30 16:21 ` Rusi
2015-05-30 16:03 ` Emanuel Berg
2015-05-30 16:32 ` Rusi [this message]
2015-05-30 16:54 ` Pascal J. Bourguignon
2015-05-30 17:10 ` Rusi
2015-05-30 19:12 ` Pascal J. Bourguignon
2015-05-29 8:28 Marcin Borkowski
2015-05-30 8:28 ` Tassilo Horn
2015-06-14 10:52 ` Marcin Borkowski
[not found] ` <mailman.4976.1434279182.904.help-gnu-emacs@gnu.org>
2015-06-14 11:31 ` Pascal J. Bourguignon
2015-06-16 23:48 ` Jim Diamond
2015-06-17 0:06 ` Emanuel Berg
2015-06-17 6:23 ` Andreas Röhler
[not found] ` <mailman.5136.1434522217.904.help-gnu-emacs@gnu.org>
2015-06-17 10:49 ` Pascal J. Bourguignon
2015-06-17 10:53 ` Pascal J. Bourguignon
2015-06-17 14:42 ` Stefan Monnier
2015-06-17 16:19 ` Andreas Röhler
2015-06-17 19:30 ` Tassilo Horn
[not found] ` <mailman.5171.1434557990.904.help-gnu-emacs@gnu.org>
2015-06-17 17:12 ` Stefan Monnier
2015-06-17 20:22 ` Emanuel Berg
2015-06-17 22:13 ` Pascal J. Bourguignon
2015-06-17 23:46 ` Emanuel Berg
2015-06-18 14:57 ` Udyant Wig
2015-06-18 15:47 ` Emanuel Berg
2015-06-19 13:49 ` Udyant Wig
2015-06-17 20:33 ` Emanuel Berg
2015-06-17 22:07 ` Robert Thorpe
2015-06-17 22:17 ` Pascal J. Bourguignon
2015-06-17 0:43 ` Pascal J. Bourguignon
2015-06-17 16:02 ` Phillip Lord
[not found] ` <mailman.5167.1434556959.904.help-gnu-emacs@gnu.org>
2015-06-23 23:49 ` Jim Diamond
[not found] ` <mailman.3950.1432974543.904.help-gnu-emacs@gnu.org>
2015-05-30 12:59 ` Pascal J. Bourguignon
2015-06-14 10:55 ` Marcin Borkowski
[not found] ` <mailman.4977.1434279342.904.help-gnu-emacs@gnu.org>
2015-06-14 20:04 ` Stefan Monnier
2015-06-14 21:44 ` Pascal J. Bourguignon
2015-06-14 21:49 ` Pascal J. Bourguignon
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=4c247f74-529f-41e4-9712-221560ff7c6c@googlegroups.com \
--to=rustompmody@gmail.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).