@dekkzz76 every day at the moment I am using orgmode and it looks like this:
#+TITLE: Today's thing
#+AUTHOR: screwtape
Sometimes a preamble
<C-c C-v d elisp> -> <explicitly load babel languages being used in this document>
Heading :maybe_properties_too:
#+name: a-good-name
#+HEADER:
<C-c C-v d lisp> -> some code
brief commentary about the code
** Subheadings being demonstrations and implications of said code
Another heading logically independent from the first.
@dekkzz76 last week I tried something a bit crazy to get a "cell editor" for lisp code instead of a generic text editor, but I can't really call it a success:
#+name: tableout
#+begin_src lisp :var input=hello-world :var check='() :results output
(let* ((string (format nil "{({a^ })%~}" input)))
(with-input-from-string (standard-input string)
(let ((read (read)))
(if check
(princ read)
(princ (eval read))))))
#+end_src
draw your own conclusions
@dekkzz76 obviously I didn't demonstrate property drawers or however it is you put global headers around #+AUTHOR: of which I always have to look up my previous examples of how to do that.
When it makes sense for emacs/orgmode to drive something, I use org-babel-lob-ingest and elisp or maybe eshell, though orgmode's eshell support is a mystery to me.
@dekkzz76 ironically, the idea of writing plain text files in order to create and use a program kinda sucks. Emacs is the ex-maclisp tradition for character editing, but emacs is really just a substrate. And the thing for it to do it comes packaged with is orgmode (life in plain text).
You don't use :session ? Honestly the annoying thing for me is changing the default package of a session.
@dekkzz76 alright it seems there's a thing, but I've always just done this recursively with org-mode's support for walking around org-files I think, but I guess it's powerful there is a sort of templating-match
Add comment