From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: "Charles C. Berry" <ccberry@ucsd.edu>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>,
John Kitchin <jkitchin@andrew.cmu.edu>
Subject: Re: tangling order
Date: Wed, 17 Feb 2016 16:43:41 +0100 [thread overview]
Message-ID: <m2y4ajgx5e.fsf@charm-ecran.irisa.fr> (raw)
In-Reply-To: <alpine.OSX.2.20.1602160909320.468@charles-berrys-macbook.local> (Charles C. Berry's message of "Tue, 16 Feb 2016 09:34:22 -0800")
[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]
On 2016-02-16 18:34, "Charles C. Berry" <ccberry@ucsd.edu> writes:
>> I've found a workaround, as it is only for a few blocks I manually
>> change their headers, so it is fine at the moment.
>
> Another workaround would be to add after advice to
> `org-babel-get-src-block-info' to map your faux languages to a common
> variant.
>
>> I still think it
>> would be great to have better control on the order in which blocks are
>> tangled.
>
> If you want to do this inside org/emacs (and not stitch a bunch of tangled
> files together with other tools), try this in your *.org file and execute
> it. The result is what you might work with (i.e. customize or advice the
> function below).
>
> #+BEGIN_SRC emacs-lisp :results pp :tangle foo.ml
> (org-babel-tangle-collect-blocks)
> #+END_SRC
Thank you for the suggestions. Looking at what this function returns
(blocks sorted by language), I now understand better why this does not
do what I want.
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
Monthly Athmospheric CO₂ (2016-01, Mauna Loa Obs.): 402.52
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
prev parent reply other threads:[~2016-02-17 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 10:19 tangling order Alan Schmitt
2016-02-16 11:42 ` John Kitchin
2016-02-16 15:22 ` Alan Schmitt
2016-02-16 17:34 ` Charles C. Berry
2016-02-17 15:43 ` Alan Schmitt [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=m2y4ajgx5e.fsf@charm-ecran.irisa.fr \
--to=alan.schmitt@polytechnique.org \
--cc=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
/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).