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

From: Tomas Grigera <tgrigera@gmail.com>
To: Eric Schulte <eric.schulte@gmx.com>
Cc: emacs-orgmode@gnu.org
Subject: [PATCH] Org manual on :noweb-ref property
Date: Sat, 31 Dec 2011 21:22:41 -0300	[thread overview]
Message-ID: <CAJMNdQL2TXVudvwxQZo0E2jOgp_u4g-s_AK-Fu0U08m_mTD59A@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 358 bytes --]

Hi

After Eric's fix a couple of days ago, setting :noweb-ref through a
property now works as explained in the manual. However, the example
given will only work if one turns on property inheritance. I think it
is worthwhile noting this in the manual. The patch here adds that
comment.

First time I send a patch, sorry if I screwd up.

Happy new year

Tomas

[-- Attachment #2: org.texi.diff --]
[-- Type: text/x-patch, Size: 680 bytes --]

diff --git a/doc/org.texi b/doc/org.texi
index 3f02efb..618b287 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -13627,7 +13627,9 @@ concatenated together to form the replacement text.
 By setting this header argument at the sub-tree or file level, simple code
 block concatenation may be achieved.  For example, when tangling the
 following Org mode file, the bodies of code blocks will be concatenated into
-the resulting pure code file.
+the resulting pure code file (note that this example needs that property
+inheritance be turned on for the @code{noweb-ref} property, see
+@ref{Property inheritance}).
 
 @example
  #+BEGIN_SRC sh :tangle yes :noweb yes :shebang #!/bin/sh

next             reply	other threads:[~2012-01-01  0:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-01  0:22 Tomas Grigera [this message]
2012-01-02 14:28 ` [PATCH] Org manual on :noweb-ref property Bastien

find likely ancestor, descendant, or conflicting patches for this message:
dfblob:3f02efb dfblob:618b287
	(help)

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=CAJMNdQL2TXVudvwxQZo0E2jOgp_u4g-s_AK-Fu0U08m_mTD59A@mail.gmail.com \
    --to=tgrigera@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=eric.schulte@gmx.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

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