emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: emacs-org list <emacs-orgmode@gnu.org>
Subject: Noweb blocks duplicate during Org export if part of #+include
Date: Thu, 6 Dec 2018 09:34:22 -0500	[thread overview]
Message-ID: <CAFyQvY180O5DBwVou3f647E2L9FVukovNpSHzjKBODdkULuRkw@mail.gmail.com> (raw)

Hello,

Here is a MWE:

1. With point on the "** Foo" section, running C-c C-e C-s h o, will
result in noweb-duplicate-bug.html with the <<some_snippet>> block
expanded only once, as expected.

2. But with point on the "* Foo Included" section, running the same
C-c C-e C-s h o, will result in foo_included.html with the
<<some_snippet>> block expanded twice! It seems like the Noweb
expansion happens first as usual, and then again when parsing
#+include (which shouldn't happen?).

=====
#+title: Noweb Duplicating Bug
#+author: Kaushal Modi

* Reused Sections
** Foo
:PROPERTIES:
:CUSTOM_ID: foo
:END:
*** Some Snippet
#+begin_src emacs-lisp :noweb-ref some_snippet
(message "Hello")
#+end_src
*** Some Snippet used again
#+begin_src emacs-lisp :noweb yes
(defun foo ()
  <<some_snippet>>
  )
#+end_src
* Foo Included
:PROPERTIES:
:EXPORT_FILE_NAME: foo_included
:END:
#+include: "./noweb-duplicate-bug.org::#foo" :only-contents t
=====


Org version, built from next branch: Org mode version 9.1.14
(release_9.1.14-1147-g6f8347 @
/home/kmodi/usr_local/apps/6/emacs/old-emacsclient/share/emacs/site-lisp/org/)

--
Kaushal Modi

             reply	other threads:[~2018-12-06 14:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-06 14:34 Kaushal Modi [this message]
2018-12-08  9:42 ` Noweb blocks duplicate during Org export if part of #+include Nicolas Goaziou
2018-12-12 18:50   ` Kaushal Modi

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=CAFyQvY180O5DBwVou3f647E2L9FVukovNpSHzjKBODdkULuRkw@mail.gmail.com \
    --to=kaushal.modi@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).