Eric Schulte wrote:
> > I presume that paredit is useful because it's a minor mode, so you can
> > enable it on an org-mode buffer (e.g. using babel).
>
> No, even for emacs-lisp code blocks I use C-c ' to edit the code in
> emacs-lisp mode. I do have "[" and "]" globally bound to
> `insert-par
Hi Nick,
Nick Dokos writes:
> Eric Schulte wrote:
>
>> ...
>> If you are going to do any serious work with lisp, I would emphatically
>> recommend using paredit-mode, and becoming friends with the Sexp
>> movement functions
>> ++
>> | C-M-f | runs th
Eric Schulte wrote:
> ...
> If you are going to do any serious work with lisp, I would emphatically
> recommend using paredit-mode, and becoming friends with the Sexp
> movement functions
> ++
> | C-M-f | runs the command paredit-forward |
> |---
Ah, heck, just forgot:
Casting Spells in Lisp
http://www.lisperati.com/casting.html
Comic book about programming in Lisp, Emacs Lisp Version available.
-- David
--
OpenPGP... 0x99ADB83B5A4478E6
Jabber dmj...@jabber.org
Email. dm...@ictsoc.de
pgpfQkHRmtNAJ.pgp
Description: PGP signatur
Eric Schulte wrote:
>[1 ]
>So,
>The way that I learned how to program in emacs lisp was mainly using two
>commands `elisp-index-search' bound to `C-h e' on my system, and most
>importantly `describe-function' bound to `C-h f'. With
>`describe-function' you can look at the source code of function
So,
The way that I learned how to program in emacs lisp was mainly using two
commands `elisp-index-search' bound to `C-h e' on my system, and most
importantly `describe-function' bound to `C-h f'. With
`describe-function' you can look at the source code of functions whose
behavior you are familia
