From: Bastien <bzg@gnu.org>
To: Vladimir Lomov <lomov.vl@gmail.com>
Cc: General discussions about Org-mode <emacs-orgmode@gnu.org>
Subject: Re: [BUG?] Is there a bug with 'noweb' header when tangling source block?
Date: Sat, 19 Apr 2014 14:56:19 +0200 [thread overview]
Message-ID: <87d2gdpjf0.fsf@bzg.ath.cx> (raw)
In-Reply-To: <20140419120014.GA942@smoon> (Vladimir Lomov's message of "Sat, 19 Apr 2014 21:00:14 +0900")
Hi Vladimir,
Vladimir Lomov <lomov.vl@gmail.com> writes:
> please consider attached example Org document 'ex.org'. There seems to
> be a problem when tangling a source block with noweb reference, without
> it source block is tangled fine.
yes, a bug I introduced myself, fixed now.
Thanks for reporting this,
--
Bastien
next prev parent reply other threads:[~2014-04-19 12:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-19 12:00 [BUG?] Is there a bug with 'noweb' header when tangling source block? Vladimir Lomov
2014-04-19 12:56 ` Bastien [this message]
2014-04-19 13:38 ` Vladimir Lomov
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=87d2gdpjf0.fsf@bzg.ath.cx \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=lomov.vl@gmail.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).