emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Lawrence Bottorff <borgauf@gmail.com>
To: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Running in-line babel code at auto-insert template file open
Date: Mon, 24 Feb 2020 21:51:08 -0600	[thread overview]
Message-ID: <CAFAhFSXZVOb4vMmoO2xqNZY7U4Q-Dwepu1pqB0dGoSvJ4Ceq8A@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1271 bytes --]

Let's say I have a standard org file I want to have created multiple times.
I've created a template file and told Emacs autoinsert where it is. Here's
the relevant in my init

(use-package autoinsert
  :ensure t
  (define-auto-insert "poolchem.org?$" "poolchem.org"))

So in this template file poolchem.org I have six table skeletons, but I
also want various customized additions. For example, I would like the table
names to reflect the current week starting with the coming Sunday's date

#+tblname: pc1-*src_emacs-lisp[:results raw]{(org-read-date nil nil "++sun"
nil (org-time-string-to-time "2020-02-24"))}*

which would hopefully show up in the newly created buffer as

#+tblname: pc1-2020-03-01

But then nothing of the sort happens, i.e., the in-line code just comes
back verbatim when I create a new file, unevaluated. I guess I'm totally
missing what is going on with in-line code. It seems other methods of
template creation allow code to be embedded, then to be evaluated. (The
variable auto-insert-alist has entire templates.) I've experimented with
eval of org-sbe in # local variables: ... but that was for running code
blocks upon file open, not individual embedded functions that would
customize my newly created org file. Any ideas?


[-- Attachment #2: Type: text/html, Size: 1677 bytes --]

             reply	other threads:[~2020-02-25  3:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-25  3:51 Lawrence Bottorff [this message]
2020-02-27  3:21 ` Running in-line babel code at auto-insert template file open Lawrence Bottorff

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:

  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=CAFAhFSXZVOb4vMmoO2xqNZY7U4Q-Dwepu1pqB0dGoSvJ4Ceq8A@mail.gmail.com \
    --to=borgauf@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).