From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: help-gnu-emacs@gnu.org,Eric Abrahamsen <eric@ericabrahamsen.net>
Subject: Re: What makes elisp fun ?
Date: Fri, 26 May 2017 14:43:56 +0000 [thread overview]
Message-ID: <1269D2ED-F5DD-4BD1-A965-3D11183C2F1E@gmail.com> (raw)
In-Reply-To: <8760gng1o2.fsf@ericabrahamsen.net>
On May 26, 2017 6:58:37 AM PDT, Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
>To that I'll add: the built-in help and debugging facilities. I am
>continually annoyed that other languages don't have edebug. *Why* don't
>they have edebug? Edebug was an essential factor in my progress from a
>novice programmer to... wherever I'm at now. Watching the little cursor
>go basically taught my brain how code flows. Now I know you're supposed
>to do it with printf statements and gdb, but in elisp it's still
>comforting to run through my functions with edebug before I go on to
>next steps.
>
>Eric
I can also say that edebug and the rich online documentation makes for a great interactive experience. Combined with the fact that you can override pretty much anything anywhere easily, experimenting is very easy and fun!
Maxim
Hi!
next prev parent reply other threads:[~2017-05-26 14:43 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 [this message]
2017-05-26 14:50 ` Yuri Khan
2017-05-26 20:53 ` Emanuel Berg
2017-05-26 21:17 ` John Ankarström
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=1269D2ED-F5DD-4BD1-A965-3D11183C2F1E@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=eric@ericabrahamsen.net \
--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.