emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Charles Millar <millarc@verizon.net>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: :eval yes use and documentation
Date: Thu, 16 Dec 2021 21:19:33 -0500	[thread overview]
Message-ID: <599bf3cc-6dbe-4010-129c-a639ecd9ae70@verizon.net> (raw)
In-Reply-To: <599bf3cc-6dbe-4010-129c-a639ecd9ae70.ref@verizon.net>

Org mode version 9.5.1 (release_9.5.1-279-g8908fb @ 
GNU Emacs 28.0.50 (build 344, x86_64-pc-linux-gnu, GTK+ Version 3.24.23, 
cairo version 1.16.0) of 2020-12-31

Here is a use case.

I have many files each with as many as 60 tables that are generated 
using ob -rec. So that the tables are not evaluated during export it is 
convenient for me to set a buffer wide

#+PROPERTY: header-args :eval never-export.

On other hand, each file may also include, under a sub-tree latex source 
code blocks for signature lines, letter heads, etc.

In another sub-tree, called correspondence, those source code blocks are 
called using :noweb yes, such as

   #+begin_src latex :noweb yes


[Body of letter]

   #+begin_src latex :noweb yes

If I include in the correspondence sub-tree
:header-args: :eval yes

the results are a complete letter, i.e. letterhead followed by the body 
and then signature line.

If I do not include the ":eval yes" property in the sub-tree, only the 
body of the letter results, as expected.

So after all that, here are some questions:

Is ":eval yes" officially allowed and, if so, why is it not documented?

Should it be?

May its use be inferred from other examples such as those from :cache or 

I found the following discussion, but it is fairly old:


Charlie Millar

       reply	other threads:[~2021-12-17  2:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <599bf3cc-6dbe-4010-129c-a639ecd9ae70.ref@verizon.net>
2021-12-17  2:19 ` Charles Millar [this message]
2022-05-06  9:54   ` Ihor Radchenko

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:

  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=599bf3cc-6dbe-4010-129c-a639ecd9ae70@verizon.net \
    --to=millarc@verizon.net \
    --cc=emacs-orgmode@gnu.org \
    --subject='Re: :eval yes use and documentation' \


* 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 inbox:


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