From: Grant Rettke <gcr@wisdomandwonder.com>
To: Rainer M Krug <Rainer@krugs.de>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
"Thomas S. Dye" <tsd@tsdye.com>
Subject: Re: Help with tangling a table into a source-code representation of the data contained within
Date: Tue, 25 Feb 2014 23:21:26 -0600 [thread overview]
Message-ID: <CAAjq1mdW6+LkFWUoijhsSvXL=2w5ecwGX8bt-_KYu72pziEP3w@mail.gmail.com> (raw)
In-Reply-To: <CAAjq1mc=ujjvtF2Y3acwOZXeNViihBRQ5nP3wSCE6bFRV7Nzgw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]
This seems like a fine option:
#+name: mode_data
| mode | paredit | auto-save |
|------------+---------+-----------|
| scheme | TRUE | TRUE |
| emacs-lisp | TRUE | TRUE |
| ielm | TRUE | FALSE |
#+begin_src emacs-lisp :var data=mode_data :exports results :file modes.json
(require 'json)
(json-encode data)
#+end_src
JSON because I will probably use it a few different ways, and most langs
today handle JSON just fine.
On Tue, Feb 25, 2014 at 10:41 PM, Grant Rettke <gcr@wisdomandwonder.com>wrote:
> Thanks everyone.
>
> My tentative plan is to run some elisp that will dump the table to an
> intermediate file and then dependent files may load it themselves.
>
--
Grant Rettke | ACM, AMA, COG, IEEE
gcr@wisdomandwonder.com | http://www.wisdomandwonder.com/
“Wisdom begins in wonder.” --Socrates
((λ (x) (x x)) (λ (x) (x x)))
“Life has become immeasurably better since I have been forced to stop
taking it seriously.” --Thompson
[-- Attachment #2: Type: text/html, Size: 1655 bytes --]
prev parent reply other threads:[~2014-02-26 5:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 4:37 Help with tangling a table into a source-code representation of the data contained within Grant Rettke
2014-02-25 4:45 ` Samuel Wales
2014-02-25 4:49 ` Thomas S. Dye
2014-02-25 9:00 ` Rainer M Krug
2014-02-26 4:41 ` Grant Rettke
2014-02-26 5:21 ` Grant Rettke [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='CAAjq1mdW6+LkFWUoijhsSvXL=2w5ecwGX8bt-_KYu72pziEP3w@mail.gmail.com' \
--to=gcr@wisdomandwonder.com \
--cc=Rainer@krugs.de \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.com \
/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).