From: Nick Dokos <nicholas.dokos@hp.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org,
Ivanov Dmitry <usr345@gmail.com>
Subject: Re: programming for org-mode
Date: Thu, 15 Jul 2010 17:40:47 -0400 [thread overview]
Message-ID: <12989.1279230047@alphaville.usa.hp.com> (raw)
In-Reply-To: Message from "Eric Schulte" <schulte.eric@gmail.com> of "Thu, 15 Jul 2010 10:26:55 PDT." <87vd8gejvk.fsf@gmail.com>
Eric Schulte <schulte.eric@gmail.com> 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 |
> |-------+------------------------------------|
> | C-M-b | runs the command paredit-backward |
> |-------+------------------------------------|
> | C-M-u | runs the command backward-up-list |
> |-------+------------------------------------|
> | C-M-k | runs the command kill-sexp |
> |-------+------------------------------------|
> | C-y | runs the command yank |
> +--------------------------------------------+
>
> They allow you to manipulate lisp code on the level of logical
> expressions, the utility of which can not be over stated.
>
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). But if you are
editing a .el file, then emacs-lisp mode provides all these facilities
(C-M-f -> forward-sexp, etc.) and you don't need paredit. Do I have
that right?
Thanks,
Nick
PS. The ultimate *reference* for emacs lisp is the Emacs Lisp Reference
manual
http://www.gnu.org/software/emacs/manual/html_node/elisp/index.html
At some point in one's emacs-lisp programming life, it will be necessary
to refer to it - but it is very much a reference manual, not a tutorial.
next prev parent reply other threads:[~2010-07-15 21:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 4:52 programming for org-mode Ivanov Dmitry
2010-07-15 17:26 ` Eric Schulte
2010-07-15 20:15 ` David Maus
2010-07-15 20:21 ` David Maus
2010-07-15 21:40 ` Nick Dokos [this message]
2010-07-15 21:53 ` Eric Schulte
2010-07-15 22:17 ` Nick Dokos
2010-08-05 12:33 ` Re[2]: " Ivanov Dmitry
[not found] ` <AANLkTi=wrOCCrZxRZTGgvNKGjy2jmnogiA91bYnHAExV@mail.gmail.com>
2010-08-06 7:33 ` Re[4]: " Ivanov Dmitry
2010-08-07 13:12 ` Re[2]: " David Maus
2010-08-07 15:29 ` Re[4]: " Ivanov Dmitry
2010-08-08 6:43 ` David Maus
2010-08-08 15:49 ` Re[6]: " Ivanov Dmitry
2010-08-09 19:16 ` David Maus
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=12989.1279230047@alphaville.usa.hp.com \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@gmail.com \
--cc=usr345@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).