emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dan Davison <dandavison7@gmail.com>
To: Jeff Horn <jrhorn424@gmail.com>
Cc: emacs-orgmode@gnu.org, Andrea Crotti <andrea.crotti.0@gmail.com>
Subject: Re: Overlays and elisp code
Date: Tue, 01 Feb 2011 10:51:23 +0000	[thread overview]
Message-ID: <m14o8o6n9w.fsf@gmail.com> (raw)
In-Reply-To: <AANLkTinsm3HajS45M8exb-pfzDw-H4oQsyNBWj8L=pEV@mail.gmail.com> (Jeff Horn's message of "Mon, 31 Jan 2011 15:04:29 -0500")

Jeff Horn <jrhorn424@gmail.com> writes:

> I can reproduce this. emacs 23.1 and org 7.4
>
> On Mon, Jan 31, 2011 at 5:04 AM, Andrea Crotti
> <andrea.crotti.0@gmail.com> wrote:
>> I found a strange behaviour which might be a bug, but maybe of my
>> configuration.
>>
>> This is org mode version:
>> Org-mode version 7.4 (release_7.4.199.g8be1.dirty)
>> and emacs:
>> "GNU Emacs 23.2.1 (x86_64-apple-darwin10.3.0, NS apple-appkit-1038.29)
>>  of 2010-05-09 on linc"
>>
>> To reproduce the bug I do
>> - go over an elisp code block
>> - C-c ' to edit in the overlay
>> - C-c ' to go back when done
>>
>> And it works perfectly, BUT if for example I remove a parenthesis before
>> pressing C-c ', I can't go back.
>>
>> C-c ' becomes undefined and I have to kill both the overlay and the
>> original buffer.
>>
>> While I was writing I also found the cause of the problem, Paredit!
>> Removing the hook from emacs-lisp-mode-hook fixes this, but paredit is
>> really useful with elisp, maybe someone has an idea of why this happens?

Hi Andrea,

So it looks like paredit-mode refuses to start up (throws an error) if
the parentheses are unbalanced. So how about we use

#+begin_src emacs-lisp
(add-hook 'emacs-lisp-mode-hook
          (lambda ()
            (condition-case nil
                (paredit-mode)
              (error (message "Failed to activate paredit mode")))))
#+end_src

At the moment this message gets stamped on by a message which
org-edit-src always issues in the echo-area. I'm going to submit a patch
to control that in a subsequent email.

Oh no. You got me editing elisp with paredit mode turned on. Maybe it
will last more than 5 minutes this time :)

Dan

>>
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Please use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>

  parent reply	other threads:[~2011-02-01 10:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-31 10:04 Overlays and elisp code Andrea Crotti
2011-01-31 20:04 ` Jeff Horn
2011-02-01  8:08   ` Andrea Crotti
2011-02-01 10:51   ` Dan Davison [this message]
2011-02-01 11:01     ` Dan Davison
2011-02-01 11:08       ` Carsten Dominik
2011-02-01 11:22         ` Dan Davison
2011-02-01 11:30           ` Carsten Dominik
2011-02-01 11:47             ` Dan Davison

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=m14o8o6n9w.fsf@gmail.com \
    --to=dandavison7@gmail.com \
    --cc=andrea.crotti.0@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jrhorn424@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).