-
-
Notifications
You must be signed in to change notification settings - Fork 74
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
Org-mode #42
Comments
Hi @joinr. Thanks for posting this issue. As I mentioned on slack, I don't use emacs, and am probably not the best person to be working on this, but I think it's a great idea, and encourage you or any one else interested to put forward a proposal. Thanks again. |
I use vega-lite with org mode. The main idea is to do this 3 steps to include a vega lite spec in a org mode file: a)
(def spec ....
(spit "spec.vl"
(json/generate-string spec)) b)
c)
|
Although @behrica's work-flows works, For example,
You may find some examples of how convenient to specify diagram with plantuml with org-mode's code block. With this support, I will be able to use org as markdown syntax to |
Hey @yubrshen. Right now, you could do something equivalent to what @behrica suggests by using If there's a way to facilitate a one step process in org-mode, I'm more than happy to accommodate that. I just don't know enough about org-mode to be of much help sorting out that side of it. The other thing I would really like to support in Oz is ingest of org-mode files and interpretation as hiccup. Perhaps we can even extend Oz's notion of parallelized clj code execution, so that you could use Oz's notebook functionality with org-mode files. I don't know how much control org-mode gives you over what sort of output formats/templates are available, but Oz is quite flexible in this regard, and only becoming more capable. So perhaps it would be useful to have a flexible rendering system (static site generation, pdf documents, etc) for org-mode files? Happy to discuss more if anything like that makes sense. Thanks again |
Adding org support as an option (in addition to existing markdown) would be useful.
The text was updated successfully, but these errors were encountered: