From: Thomas S. Dye <tsd@tsdye.com>
To: Jarmo Hurri <jarmo.hurri@iki.fi>
Cc: emacs-orgmode@gnu.org
Subject: Re: Local variables in an org file
Date: Fri, 21 Aug 2015 07:08:02 -1000 [thread overview]
Message-ID: <m2a8tkbmdp.fsf@tsdye.com> (raw)
In-Reply-To: <87twrssyhy.fsf@iki.fi>
Aloha Jarmo,
Jarmo Hurri <jarmo.hurri@iki.fi> writes:
> Thomas S. Dye <tsd@tsdye.com> writes:
>
>> * Define a local variable
>> #+name: my-var
>> #+header: :exports none
>> #+begin_src R
>> 768
>> #+end_src
>> #+name: pass-my-var-to-code-block
>> #+header: :var x=my-var
>> #+header: :exports both
>> #+begin_src emacs-lisp
>> (+ x 1)
>> #+end_src
>>
>> #+results: pass-my-var-to-code-block
>> : 769
>>
>> The variable is call_my-var().
>
> Yeah, this will work, but it's a huge amount of work.
>
> It would be brilliant if one could easily refer to a property inside a
> subtree. In both text and code.
#+SELECT_TAGS: export
#+EXCLUDE_TAGS: noexport
* Define a my-var property
:PROPERTIES:
:my-var: 768
:END:
#+name: pass-property-to-code-block
#+header: :var my-var=(string-to-number (jk-org-kwd "my-var"))
#+header: :exports both
#+begin_src emacs-lisp
(+ my-var 1)
#+end_src
#+results: pass-property-to-code-block
: 769
The variable =my-var= is call_jk-org-kwd("my-var").
* Access keyword values :noexport:
This is taken from [[http://jkitchin.github.io/blog/2013/05/05/Getting-keyword-options-in-org-files/][John Kitchin's blog]]. It has been modified so
=org-element-map= returns node properties in addition to keywords.
#+name: jk-keywords
#+header: :results silent
#+begin_src emacs-lisp
(defun jk-org-kwds ()
"parse the buffer and return a cons list of (property . value)
from lines like: #+PROPERTY: value"
(org-element-map (org-element-parse-buffer 'element) '(keyword node-property)
(lambda (keyword) (cons (org-element-property :key keyword)
(org-element-property :value keyword)))))
#+end_src
#+name: jk-org-kwd
#+header: :noweb yes
#+header: :var KEYWORD=""
#+begin_src emacs-lisp
<<jk-keywords>>
(cdr (assoc KEYWORD (jk-org-kwds)))
#+end_src
This might be a huge amount of work, too, but it keeps the variable in a
property instead of a source code block.
I keep John Kitchin's code in the library of Babel so that part doesn't
need to be reproduced each time.
Here is the ascii output:
1 Define a my-var property
==========================
,----
| (+ my-var 1)
`----
,----
| 769
`----
The variable `my-var' is `768'.
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
prev parent reply other threads:[~2015-08-21 17:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 6:39 Local variables in an org file Jarmo Hurri
2015-08-21 2:23 ` Grant Rettke
2015-08-21 2:52 ` Thomas S. Dye
2015-08-21 10:54 ` Jarmo Hurri
2015-08-21 11:57 ` Rainer M Krug
2015-08-21 17:08 ` Thomas S. Dye [this message]
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=m2a8tkbmdp.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=jarmo.hurri@iki.fi \
/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).