From: john@ankarstrom.se (John Ankarström)
To: help-gnu-emacs@gnu.org
Subject: Re: What makes elisp fun ?
Date: Fri, 26 May 2017 23:17:14 +0200 [thread overview]
Message-ID: <87d1avjp2d.fsf@ankarstrom.se> (raw)
In-Reply-To: <yw.86poevfigw.fsf@zoho.com> (Emanuel Berg's message of "Fri, 26 May 2017 22:53:19 +0200")
Emanuel Berg <moasen@zoho.com> writes:
> Eric Abrahamsen wrote:
>
>> This is a trick question: the reason elisp is fun is
>> because it's the Emacs extension language.
>
> Are you sure? I can't even imagine having to do C or an OO
> language for what I do in Elisp. How it would ever work is
> another issue. But I can even less imagine it be as much
> fun as Lisp. Lisp is just a more relaxed language and for
> programming which is so intense and focused it is an
> awesome quality.
I completely agree with this sentiment. Emacs Lisp is a joy
to work with not only because it's the interactive extension
language of Emacs, but because it's a nice language. If
Emacs used Python as an extension language, I don't think we
would feel the same for Python as we do for Elisp.
The fact that Elisp is part of Emacs helped me discover, not
as a means to an end, but as a language in its own right.
next prev parent reply other threads:[~2017-05-26 21:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 12:28 What makes elisp fun ? Jean-Christophe Helary
2017-05-22 21:36 ` Emanuel Berg
2017-05-22 21:49 ` Emanuel Berg
2017-05-23 22:39 ` Michael Heerdegen
2017-05-23 22:49 ` Drew Adams
2017-05-24 9:13 ` hector
2017-05-24 9:29 ` tomas
2017-05-24 20:56 ` Emanuel Berg
2017-05-26 10:52 ` Thien-Thi Nguyen
2017-05-26 13:58 ` Eric Abrahamsen
2017-05-26 14:43 ` Maxim Cournoyer
2017-05-26 14:50 ` Yuri Khan
2017-05-26 20:53 ` Emanuel Berg
2017-05-26 21:17 ` John Ankarström [this message]
2017-05-28 18:35 ` Emanuel Berg
2017-05-28 18:48 ` John Ankarström
2017-05-28 22:22 ` Emanuel Berg
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d1avjp2d.fsf@ankarstrom.se \
--to=john@ankarstrom.se \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.