emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Grant Rettke <gcr@wisdomandwonder.com>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Help with tangling a table into a source-code representation of the data contained within
Date: Mon, 24 Feb 2014 22:37:58 -0600	[thread overview]
Message-ID: <CAAjq1mcoXHxHkD9RoVc0Lz1fQhm0e47iGd3B5wL5mOeCcGwtyw@mail.gmail.com> (raw)

Hi,

My goal is to define a table in org-mode, display it nicely to humans
using export, and tangle that same data table into
an elisp data structure for use elsewhere within the program. It might
look something like this:

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

* Modes

This is a place for humans to keep track both of what
modes activated for what file types; and also what utilies are used
with those modes when they are activated.

#+tblname: modes_data
| mode name | file_type | paredit | auto-save |
|-----------+-----------+---------+-----------|
| scheme | .scm  | yes     | yes       |
| elisp     | .el       | yes     | yes       |
| ielm      | nil       | yes     | no        |

* Test

#+begin_src emacs-lisp :noweb tangle :tangle test.el
  (mapcar (lambda (row) (message (car row))) modes_data)
#+end_src

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

The problem right now is that modes_data is referenced but not defined
anywhere in the tangled file.
How do I include the data itself from modes_data as an elisp data
structure to be defined during the tangling?

What I need help with is:

1. Is the goal I seek realistic?
2. What am I doing wrongly?

An alternative that I figured would work fine is to define modes_data
in a code block with elisp and export
that in the tangling; it would be nicer to use the org table features though.

Regards,

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

next             reply	other threads:[~2014-02-25  4:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-25  4:37 Grant Rettke [this message]
2014-02-25  4:45 ` Help with tangling a table into a source-code representation of the data contained within 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

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=CAAjq1mcoXHxHkD9RoVc0Lz1fQhm0e47iGd3B5wL5mOeCcGwtyw@mail.gmail.com \
    --to=gcr@wisdomandwonder.com \
    --cc=emacs-orgmode@gnu.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

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