emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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 18:17:02 -0400	[thread overview]
Message-ID: <14300.1279232222@alphaville.usa.hp.com> (raw)
In-Reply-To: Message from "Eric Schulte" <schulte.eric@gmail.com> of "Thu, 15 Jul 2010 14:53:14 PDT." <87fwzkbeet.fsf@gmail.com>

Eric Schulte <schulte.eric@gmail.com> 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-parenthesis' and `move-past-close-and-reindent' respectively,
> but that's probably a little too radical for most users.
> 
> I only enable paredit minor-mode in lispy modes.
> 

Ah, OK.

> > 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?
> >
> 
> Not quite,
> 
> Paredit has a number of nice features aside from sexp movement,
> including /electric/ insertion of both open and close parenthesis,
> brackets and quotation's which greatly increase the speed with which one
> can write lisp code -- all the while ensuring that the code in the
> buffer is /valid/ in terms of balanced parenthesis.
> 

Thanks for the explanation!

Nick

  reply	other threads:[~2010-07-15 22:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-15  4:52 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
2010-07-15 21:53     ` Eric Schulte
2010-07-15 22:17       ` Nick Dokos [this message]
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=14300.1279232222@alphaville.usa.hp.com \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=schulte.eric@gmail.com \
    --cc=usr345@gmail.com \
    --subject='Re: programming for org-mode' \
    /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

Code repositories for project(s) associated with this 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).