From: Bernt Hansen <bernt@norang.ca>
To: emacs-orgmode@gnu.org
Subject: Bug: Can't edit example blocks [7.9.2 (release_7.9.2-781-g5de94e @ /home/bernt/git/org-mode/lisp/)]
Date: Tue, 25 Dec 2012 17:12:07 -0500 [thread overview]
Message-ID: <87pq1xok7c.fsf@norang.ca> (raw)
The following source blocks refer to http://doc.norang.ca/org-mode.org
org-mode.org line 1553
#+begin_example
Default Task
[d] norang Organization <-- Task B
The task interrupted by starting the last one
[i] norang Organization <-- Task B
Current Clocking Task
[c] org NEXT Document my use of org-mode <-- Task A
Recent Tasks
[1] org NEXT Document my use of org-mode <-- Task A
[2] norang Organization <-- Task B
...
[Z] org DONE Fix default section links <-- 35 clock task entries ago
#+end_example
C-c ' in the example block gives
#+begin_example
Debugger entered--Lisp error: (error "No special environment to edit here")
signal(error ("No special environment to edit here"))
user-error("No special environment to edit here")
org-edit-special()
call-interactively(org-edit-special nil nil)
#+end_example
This used to work in previous org versions
Usecase: I find it convenient to edit in a separate buffer, select
everything with C-x h, cut it and replace it than working on
the data in the example block. When example blocks are
indented in list entries org-edit-special automatically
indents the contents inside the indented #+begin_example
... #+end_example lines already properly indented for the
list.
Emacs : GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.0)
of 2010-12-11 on raven, modified by Debian
Package: Org-mode version 7.9.2 (release_7.9.2-781-g5de94e @ /home/bernt/git/org-mode/lisp/)
next reply other threads:[~2012-12-25 22:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-25 22:12 Bernt Hansen [this message]
2012-12-29 10:21 ` Bug: Can't edit example blocks [7.9.2 (release_7.9.2-781-g5de94e @ /home/bernt/git/org-mode/lisp/)] Bastien
2012-12-30 20:20 ` Bernt Hansen
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=87pq1xok7c.fsf@norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@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 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).