From: Ken Mankoff <mankoff@gmail.com>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: org-babel-expand-src-block behavior
Date: Sat, 12 Aug 2017 06:40:47 +0200 [thread overview]
Message-ID: <m28tipl7ow.fsf@gmail.com> (raw)
Hi,
I've just learned about =org-babel-expand-src-block= (from [1]) which seems like an improvement over =org-edit-special=, because variables are expanded.
But I notice two issues with it, and I'm wondering if these are intentional or bugs, or if there are work-arounds.
First, the buffer is read-only (which someone else claims is a bug [2]), and second, if I make changes and then exit the expanded block (via C-') without saving, the changes are lost. If I enter =org-edit-special= and exit w/o saving, the changes are propagated back to the buffer.
Cheers,
-k.
Org version:
Org mode version 9.0.9 (9.0.9-68-g492420-elpaplus @ /Users/mankoff/.emacs.d/elpa/org-plus-contrib-20170807/)
[1] https://emacs.stackexchange.com/questions/34821/pass-variable-from-src-block-to-org-edit-src-code
[2] https://emacs.stackexchange.com/questions/29368/org-babel-noweb-expansion-when-sending-c-c-buffer-to-python-shell
next reply other threads:[~2017-08-12 4:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-12 4:40 Ken Mankoff [this message]
2017-08-12 10:52 ` org-babel-expand-src-block behavior Nicolas Goaziou
2017-08-12 18:11 ` Ken Mankoff
2017-08-14 14:25 ` Nicolas Goaziou
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=m28tipl7ow.fsf@gmail.com \
--to=mankoff@gmail.com \
--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).