-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automatic creation of demo-it steps from an org file #18
Milestone
Comments
Interesting suggestion. Would you think that a function that generated the steps (which would allow you to add/change the steps) be a good idea?
… On Feb 13, 2019, at 11:35 PM, Vegard Vesterheim ***@***.***> wrote:
A feature request:
Given an org-file containing some headings and some source-code blocks containing named shell-commands, it should be possible to auto-generate the demo-it steps for presenting this org-file. Each heading becomes demo-it-presentation-advance and each code-block becomes demo-it-run-in-shell.
It is possible to handcraft the demo-it recipe, but it becomes cumbersome when editing the presentation and trying to keep the demo-it steps in sync.
It should be possible to parse the org-file using something like org-element-parse-buffer, and autogenerate the steps.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#18>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAejjXdQthV3u8TbtpJZrDXns3H5B9THks5vNRHWgaJpZM4a7AIr>.
|
On Thu, 14 Feb 2019 20:29:02 -0800 Howard Abrams ***@***.***> wrote:
Interesting suggestion. Would you think that a function that generated
the steps (which would allow you to add/change the steps) be a good
idea?
Yes, that would be a really useful first step.
I have a org file containing some headings and some
named sh source blocks. At the end of this org file I have manually
created an emacs-lisp block which contains the 'demo-it-create' macro
for presenting the same org file. Since my sh-source-blocks are named, I
can refer to them in the demo-it steps file like this:
(demo-it-run-in-shell "<<dynamic_inventory>>")
This means that the demo-it-steps must be part of the self-same file
which containts these named blocks. (But, according to the manual,
org-mode is also able to call named blocks from other files, maybe this
can be used to have the demo-it recipe in a separate file?)
Having a function that created this elisp-code which could then be
edited manually afterwards would be useful.
…--
- Vegard V -
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A feature request:
Given an org-file containing some headings and some source-code blocks containing named shell-commands, it should be possible to auto-generate the demo-it steps for presenting this org-file. Each heading becomes
demo-it-presentation-advance
and each code-block becomesdemo-it-run-in-shell
.It is possible to handcraft the demo-it recipe, but it becomes cumbersome when editing the presentation and trying to keep the demo-it steps in sync.
It should be possible to parse the org-file using something like
org-element-parse-buffer
, and autogenerate the steps.The text was updated successfully, but these errors were encountered: