From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: [Babel] Installation notes for an app
Date: Thu, 28 Oct 2010 17:10:32 +0200 [thread overview]
Message-ID: <801v7a8iaf.fsf@mundaneum.com> (raw)
#+TITLE: Installation Notes for an app
#+LANGUAGE: en_US
* Global constants
** Development
#+tblname: dev-params
| serverName | host1 |
| appBaseDir | /cygdrive/d/dir1 |
** Staging
#+tblname: stg-params
| serverName | host2 |
| appBaseDir | /cygdrive/d/dir2 |
** Production
#+tblname: prd-params
| serverName | host3 |
| appBaseDir | /cygdrive/d/dir3 |
* Show the params :dev:
** Statically assigned
#+begin_src sh :rownames no :var data=dev-params :exports both
echo $data
#+end_src
#+results:
: serverName host1 appBaseDir /cygdrive/d/dir1
** "Dynamically" assigned
Trying to be as adaptable as possible, I'll use the tag to refer to the right
table:
#+begin_src sh :rownames no :var data=(concat (car (org-get-tags-at (point))) "-params") :exports both
echo $data
#+end_src
#+results:
: dev-params
XXX I expected to see here the same results as in the [[*Statically%20assigned][previous version]].
PS- Instead of a tag, I could use as well some other sort of "global
constant". Right now, I do not see yet the respective gains or problems of
both. I guess I'll do in the coming days.
* Export the params
To export the params to the shell, I can process the above string with AWK or
some such.
XXX Any advice on doing it better?
Best regards,
Seb
--
Sébastien Vauban
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
reply other threads:[~2010-10-28 15:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=801v7a8iaf.fsf@mundaneum.com \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
/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).