From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas S. Dye Subject: Re: obtain ob-template.el for Babel language extension Date: Sat, 12 Sep 2015 07:15:37 -1000 Message-ID: References: <20150910222354.743ce9f2@gauss> <20150911073700.356f5760@gauss> <20150911211305.295d8ff4@gauss> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50098) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZaoP7-0004AP-Gg for emacs-orgmode@gnu.org; Sat, 12 Sep 2015 13:15:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZaoP2-0006x9-HQ for emacs-orgmode@gnu.org; Sat, 12 Sep 2015 13:15:57 -0400 Received: from gproxy1-pub.mail.unifiedlayer.com ([69.89.25.95]:36091) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1ZaoP2-0006p6-AA for emacs-orgmode@gnu.org; Sat, 12 Sep 2015 13:15:52 -0400 In-reply-to: <20150911211305.295d8ff4@gauss> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Joe Riel Cc: emacs-orgmode@gnu.org Aloha Joe, Joe Riel writes: > > No offense, but the help pages on the code blocks could really use > improvement. Glad to have your help. The documentation is a community effort. > For example, > > Exporting code blocks > --------------------- > Nowhere does this section explain *how* you can export a code block, > nor are there any links to pages that are helpful. As a minimum it > should include the relevant commands and the key bindings for > exporting code blocks. Where are they? Typically, one doesn't export a code block by itself. Instead, one exports a document that includes one or more code blocks. How to export a document is covered in Chapter 12, Exporting. > Evaluating code blocks > ---------------------- > The second paragraph states that only 'emacs-lisp' is enabled by > default. Suppose I want to use something other than 'emacs-lisp', > *how* do I enable that? The parenthetical comment states that the > Languages section lists the supoported languages but doesn't mention > that the explanation of enabling other languages is there. Better > to not leave the reader hanging. How about this: > > "By default, the evaluation facility is only enabled for Lisp code > blocks specified as ‘emacs-lisp’. See _Languages_ for instructions on > enabling other languages and for a list of supported languages. See > _Structure of code blocks_ for information on the syntax used to > define a code block." I think this is an improvement. IMHO it is almost always a good thing to get rid of parenthetical statements. Would you like to submit a patch for org.texi? You'll find instructions here: http://orgmode.org/worg/org-contribute.html#orgheadline1 Another problem is the outdated list of supported languages in Section 14.7, Languages. Perhaps this could be replaced by a pointer to the more complete list maintained on Worg? Should this section distinguish the various levels of "support", e.g. core, contrib, and packages? All the best, Tom -- Thomas S. Dye http://www.tsdye.com