emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Aaron Ecay <aaronecay@gmail.com>
To: Grant Rettke <gcr@wisdomandwonder.com>,
	"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: file-truename: Variable binding depth exceeds max-specpdl-size when tangling
Date: Wed, 20 Aug 2014 17:25:51 -0400	[thread overview]
Message-ID: <87r40argyo.fsf@gmail.com> (raw)
In-Reply-To: <CAAjq1mf2hVDOEY+2LM9LKbnW=MkE72icg-VqeiAGgXwSc37h0Q@mail.gmail.com>

Hi Grant,

2014ko abuztuak 20an, Grant Rettke-ek idatzi zuen:
> 
> Good afternoon,
> 
> While debugging one of my babel documents, I re-read [this]
> documentation on `:noweb-ref'.
> 
> What I had wanted to do was to define a bunch of source blocks and then
> at the end of the heading to tangle them all into a file. This was just
> a natural thing to do while /in the flow/ and *not* thinking about the
> document structure.
> 
> Here is the simplest possible example.
> 
> ,----
> |
> | * Demo
> |   :PROPERTIES:
> |   :noweb-ref: demo
> |   :END:
> |
> | #+begin_src emacs-lisp
> | (message "demo")
> | #+end_src
> |
> | #+begin_src emacs-lisp
> | (message "this")
> | #+end_src
> |
> | #+begin_src sh :tangle ~/tmp/demo.el :noweb yes
> | «demo»
> | #+end_src
> `----

Because the to-be-tangled code block is also under the headline with the
:noweb-ref property, it will try to include itself inside itself,
leading to an infinite regress.  Adding a headline before the third code
block fixes the issue.

-- 
Aaron Ecay

      reply	other threads:[~2014-08-20 21:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-20 21:19 file-truename: Variable binding depth exceeds max-specpdl-size when tangling Grant Rettke
2014-08-20 21:25 ` Aaron Ecay [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=87r40argyo.fsf@gmail.com \
    --to=aaronecay@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=gcr@wisdomandwonder.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).