From: "Berry, Charles" <ccberry@ucsd.edu>
To: "Yury G. Kudryashov" <urkud@urkud.name>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Edit whole session with org-edit-src-edit
Date: Mon, 9 Oct 2017 02:40:09 +0000 [thread overview]
Message-ID: <793E22AA-A516-4DDC-A61C-067D9B4735E3@ucsd.edu> (raw)
In-Reply-To: <87vajpl00m.fsf@urkud.name>
> On Oct 8, 2017, at 3:58 PM, Yury G. Kudryashov <urkud@urkud.name> wrote:
>
> Hello,
>
> I want to use orgmode for literate programming with Coq.
> I like the "edit in major mode" org-edit-src-edit feature, but it
> exports only the current src block to the temprorary buffer, so it's
> impossible to debug the file in the temporary buffer using coq-mode
> (proofgeneral) "phrase by phrase" execution.
>
> I think that some other languages may have similar problems. Say,
> code completion works better, if the whole file is available.
I used the babel jump facility proposed here:
From: Andrew Kirkpatrick <ubermonk@gmail.com>
Subject: Jumping between source blocks in a file
Message-ID: <CAHo11d5aOTLAbR1gy9+9=h_zBgTREpg7HLfLTDuhUYyBwgFDKA@mail.gmail.com>
Archived-At: <http://permalink.gmane.org/gmane.emacs.orgmode/103130>
It is not `all blocks in one buffer', but by jumping from one to the next I get much the same effect. Any changes in a block get written back to the org buffer when you jump to the next block. Binding the `*-next' function to meta-down and `*-previous' to `meta-up' makes navigation intuitive.
HTH,
Chuck
next prev parent reply other threads:[~2017-10-09 2:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-08 22:58 Edit whole session with org-edit-src-edit Yury G. Kudryashov
2017-10-09 2:40 ` Berry, Charles [this message]
2017-10-09 11:28 ` urkud
2017-10-10 7: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=793E22AA-A516-4DDC-A61C-067D9B4735E3@ucsd.edu \
--to=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=urkud@urkud.name \
/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).