From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ilya Shlyakhter Subject: inline source code blocks Date: Wed, 5 Mar 2014 16:28:00 -0500 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37172) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WLJMU-0004mr-2i for emacs-orgmode@gnu.org; Wed, 05 Mar 2014 16:28:22 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WLJMT-0006jC-8p for emacs-orgmode@gnu.org; Wed, 05 Mar 2014 16:28:22 -0500 Received: from mail-oa0-x233.google.com ([2607:f8b0:4003:c02::233]:35759) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WLJMT-0006j4-4S for emacs-orgmode@gnu.org; Wed, 05 Mar 2014 16:28:21 -0500 Received: by mail-oa0-f51.google.com with SMTP id i4so1649770oah.24 for ; Wed, 05 Mar 2014 13:28:20 -0800 (PST) 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: emacs-orgmode Some questions about inline source code blocks: - They're not fontified even when org-src-fontify-natively is true -- correct? - They're not included in tangled code; is that intended behavior? The manual does not seem to say they're different from normal code blocks, except for syntax. There are also mailing list messages that suggest they're not meant to be exported. What is the correct understanding? I can submit a patch to the manual once I understand this myself. - For very short code snippets (1-2 lines), it would be good to allow specifying (via properties) a default language for code blocks (say C) and a prefix character (say '>'), after which one could write > int i; and have this be the equivalent of +BEGIN_SRC c int i; +END_SRC by analogy with short literal examples : such as this Would this break any Org invariants? (Context: trying to use Org for literate programming in C++; interested in others' experience in this area). Thanks, Ilya