emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Erik Iverson <eriki@ccbr.umn.edu>
To: Maurizio Vitale <mav@google.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: [babel] "tangle" results of source blocks?
Date: Mon, 08 Nov 2010 15:36:15 -0600	[thread overview]
Message-ID: <4CD86D4F.2090402@ccbr.umn.edu> (raw)
In-Reply-To: <xotjd3qfh5za.fsf@google.com>

Unfortunately I can't look this up at the moment, but
my guess is that the :results code option might help with
what you want?

Maurizio Vitale wrote:
>>>>>> "Sébastien" == Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> writes:
> 
>     Sébastien> Hello Maurizio,
>     Sébastien> Maurizio Vitale wrote:
>     >> Hi, I have procmail rules defined in a org table which is then
>     >> used as an argument for an elisp block which produces procmailrc
>     >> results.
>     >> 
>     >> Something like:
>     >> 
>     >> #+tblname: mailing-lists | to | emacs-users | emacs-users |
>     >> #+TBLFM:
>     >> 
>     >> #+srcname: procmail-rules(mailing-lists=mailing-lists)
>     >> #+begin_src emacs-lisp :exports results :results output :tangle
>     >> no ... elisp code that evaluates to procmail rules #+end_src
>     >> 
>     >> #+results: procmail-rules :tangle /tmp/YYY :0: *
>     >> ^TO_emacs-users@XXX.com
>     >> $MAILDIR/emacs-users/
>     >> 
>     >> I'd like to tangle the result section, not the code block. Is
>     >> that possible?
> 
>     Sébastien> See the "exports" header argument.
> 
>     Sébastien> http://orgmode.org/manual/exports.html#exports
> 
> That option controls what is exported, but I really need to tangle:
> there're portions of the file, section headings and other documentation
> that don't belong into the output file. So for instance given:
> 
> * Introduction
>   This is a file that does blah
> * Configuration
> #+tblname: config
> |a | nice table|
> 
> *Details
> #+srcname: procmail-rules(config=config)
> #+begin_src emacs-lisp :exports results :results output :tangle ~/.procmailrc
>  ... elisp code that evaluates to procmail rules  
> #+end_src
> 
> Of this entire file, noting should end up in ~/.procmailrc except for the
> result of the evaluation of procmail-rules, which is what I hoped to
> achieve with ':tangle ~/.procmailrc' and ':exports results' combined.
> 
> Thanks,
> 
>         Maurizio
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2010-11-08 21:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-07 14:58 [babel] "tangle" results of source blocks? Maurizio Vitale
2010-11-08 20:15 ` Sébastien Vauban
2010-11-08 21:15   ` Maurizio Vitale
2010-11-08 21:36     ` Erik Iverson [this message]
2010-11-08 20:40 ` Eric Schulte
2010-11-08 21:27   ` Maurizio Vitale

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=4CD86D4F.2090402@ccbr.umn.edu \
    --to=eriki@ccbr.umn.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=mav@google.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).