From: Ken Mankoff <mankoff@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: org-babel-expand-src-block behavior
Date: Sat, 12 Aug 2017 20:11:40 +0200 [thread overview]
Message-ID: <CAFdBzEqEgfbcQ5=LXRuMgAzrsrfyNTBW=-WSBo-Y8Kcuej=agA@mail.gmail.com> (raw)
In-Reply-To: <87wp693voj.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1647 bytes --]
On Sat, Aug 12, 2017 at 12:52 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
>
> Ken Mankoff <mankoff@gmail.com> writes:
>
> > 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.
>
> I don't understand. "C-c '" is `org-edit-special'. "C-'" is
> `org-cycle-agenda-files'.
>
Typo. I meant C-c '.
> If you use "C-c '", make changes to the remote editing buffer and exit
> with "C-c '", changes are propagated to the source buffer. Remote
> editing is just a convenient way to edit another part of the same
> buffer.
>
OK. I think I have a slightly different workflow, or desired workflow. I
often *run* code in the org-edit-special buffer. I find it is useful to
debug and evaluate there as I develop it, have the Python or other REPL
(using session) also available, etc. Then when the development matures,
save changes to the source buffer and evaluate it from there in the future.
This works, but not if I'm debugging something with a variable. I got
excited when I discovered org-babel-expand-src-block because now I can more
easily debug code with input variables. But apparently this is not the
purpose of that function, since a) the buffer is read-only and b) if
read-only mode is changed, the changes are not always sent back to the
primary buffer.
Is there a way to get variables into org-edit-special? Maybe by pre-pending
C-u to C-c '? How do others debug code with input variables? Would others
like this enough to make it a feature request?
Thanks,
-k.
[-- Attachment #2: Type: text/html, Size: 2516 bytes --]
next prev parent reply other threads:[~2017-08-12 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-12 4:40 org-babel-expand-src-block behavior Ken Mankoff
2017-08-12 10:52 ` Nicolas Goaziou
2017-08-12 18:11 ` Ken Mankoff [this message]
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='CAFdBzEqEgfbcQ5=LXRuMgAzrsrfyNTBW=-WSBo-Y8Kcuej=agA@mail.gmail.com' \
--to=mankoff@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).