From: Brian Gough <bjg@network-theory.co.uk>
To: emacs-orgmode@gnu.org
Cc: Barry Gidden <barryg@network-theory.co.uk>,
Brian Gough <bjg@network-theory.co.uk>
Subject: [PATCH] tangling is not a widely-known term, describe it as literate programming
Date: Wed, 8 Dec 2010 21:05:32 +0000 [thread overview]
Message-ID: <1291842341-15199-10-git-send-email-bjg@network-theory.co.uk> (raw)
In-Reply-To: <1291842341-15199-9-git-send-email-bjg@network-theory.co.uk>
---
doc/org.texi | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index 1a2b3dd..930f948 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -770,7 +770,7 @@ create dynamic @i{agenda views}.
Org mode contains the Org Babel environment which allows you to work with
embedded source code blocks in a file, to facilitate code evaluation,
-documentation, and tangling.
+documentation, and literate programming techniques.
Org's automatic, context-sensitive table editor with spreadsheet
capabilities can be integrated into any major mode by activating the
@@ -11103,7 +11103,8 @@ Source code can be included in Org-mode documents using a @samp{src} block,
Org-mode provides a number of features for working with live source code,
including editing of code blocks in their native major-mode, evaluation of
-code blocks, tangling of code blocks, and exporting code blocks and their
+code blocks, converting code blocks into source files (known as @dfn{tangling}
+in literate programming), and exporting code blocks and their
results in several formats. This functionality was contributed by Eric
Schulte and Dan Davison, and was originally named Org-babel.
--
1.6.0.6
next prev parent reply other threads:[~2010-12-08 21:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 21:05 [PATCH] use @result{} instead of --> (looks nicer) Brian Gough
2010-12-08 21:05 ` [PATCH] use macro for @LaTeX name Brian Gough
2010-12-08 21:05 ` [PATCH] make use of the provided @ie and @eg macros to fix the spacing Brian Gough
2010-12-08 21:05 ` [PATCH] fix commas that should be full stops, semicolons or emdashes Brian Gough
2010-12-08 21:05 ` [PATCH] fix plain text that looks better with markup Brian Gough
2010-12-08 21:05 ` [PATCH] use kbd font Brian Gough
2010-12-08 21:05 ` [PATCH] improvements to wording style Brian Gough
2010-12-08 21:05 ` [PATCH] include explanations of how to look up a docstring Brian Gough
2010-12-08 21:05 ` [PATCH] use a full sentence Brian Gough
2010-12-08 21:05 ` Brian Gough [this message]
2010-12-08 21:05 ` [PATCH] make "time stamps" consistent with timestamps Brian Gough
2010-12-08 21:05 ` [PATCH] make explanation of keyword lines clearer Brian Gough
2010-12-08 21:05 ` [PATCH] use emdashes when needed Brian Gough
2010-12-08 21:05 ` [PATCH] put emacs functions in code font Brian Gough
2010-12-08 21:05 ` [PATCH] use code font for example footnote labels Brian Gough
2010-12-08 21:05 ` [PATCH] fix missing word in math formatting section Brian Gough
2010-12-08 21:05 ` [PATCH] typo/grammar fix for .done CSS explanation Brian Gough
2010-12-08 21:05 ` [PATCH] explain how to check the default version of Org Brian Gough
2010-12-08 21:05 ` [PATCH] add index entries Brian Gough
2011-02-01 11:37 ` [Accepted] " Bastien Guerry
2011-02-01 11:36 ` [Accepted] explain how to check the default version of Org Bastien Guerry
2011-02-01 11:34 ` [Accepted] typo/grammar fix for .done CSS explanation Bastien Guerry
2011-02-01 11:33 ` [Accepted] use code font for example footnote labels Bastien Guerry
2011-02-01 11:32 ` [Accepted] put emacs functions in code font Bastien Guerry
2011-02-01 11:29 ` [Accepted] make "time stamps" consistent with timestamps Bastien Guerry
2010-12-09 17:38 ` [PATCH] include explanations of how to look up a docstring Giovanni Ridolfi
2011-01-26 17:33 ` [Accepted] use @result{} instead of --> (looks nicer) Bastien Guerry
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=1291842341-15199-10-git-send-email-bjg@network-theory.co.uk \
--to=bjg@network-theory.co.uk \
--cc=barryg@network-theory.co.uk \
--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).