From: Marco Wahl <marcowahlsoft@gmail.com>
To: Nuno Salgado <nuno@salgado.eu>
Cc: Emacs-orgmode@gnu.org
Subject: Re: noweb
Date: Thu, 23 Jan 2020 08:58:21 +0100 [thread overview]
Message-ID: <84v9p2vc2q.fsf@gmail.com> (raw)
In-Reply-To: <87d0bbqbq8.fsf@nulle1.home> (Nuno Salgado's message of "Thu, 23 Jan 2020 00:04:47 +0000")
Nuno Salgado <nuno@salgado.eu> writes:
> My question was to figure out what's the point to tangle the code
> without substituition!
Your imagination is the limit. E.g. this could be useful to document
the ":noweb eval" behavior opposed to ":noweb yes".
next prev parent reply other threads:[~2020-01-23 7:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 19:41 noweb Nuno Salgado
2020-01-22 20:21 ` noweb Marco Wahl
2020-01-23 0:04 ` noweb Nuno Salgado
2020-01-23 7:58 ` Marco Wahl [this message]
2020-01-22 22:14 ` noweb Diego Zamboni
2020-01-23 0:18 ` noweb Nuno Salgado
2020-01-23 7:00 ` noweb Fraga, Eric
2020-01-23 19:17 ` noweb Nick Dokos
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=84v9p2vc2q.fsf@gmail.com \
--to=marcowahlsoft@gmail.com \
--cc=Emacs-orgmode@gnu.org \
--cc=nuno@salgado.eu \
/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).