From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: indentation across multiple source blocks Date: Sun, 23 Dec 2012 09:50:37 +0100 Message-ID: <87wqw9rw2q.fsf@bzg.ath.cx> References: <87vcbzgv8s.fsf@bzg.ath.cx> <47A50096-2C70-4C51-96E0-F0AB475DC2B7@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:51596) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TmhGg-0002s0-TP for emacs-orgmode@gnu.org; Sun, 23 Dec 2012 03:50:52 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TmhGa-0006U0-6h for emacs-orgmode@gnu.org; Sun, 23 Dec 2012 03:50:46 -0500 Received: from mail-we0-f170.google.com ([74.125.82.170]:39841) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TmhGa-0006Tw-06 for emacs-orgmode@gnu.org; Sun, 23 Dec 2012 03:50:40 -0500 Received: by mail-we0-f170.google.com with SMTP id r1so2897654wey.15 for ; Sun, 23 Dec 2012 00:50:39 -0800 (PST) In-Reply-To: <47A50096-2C70-4C51-96E0-F0AB475DC2B7@gmail.com> (Tony Day's message of "Wed, 19 Dec 2012 12:08:55 +1100") 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: Tony Day Cc: emacs-orgmode@gnu.org Hi Tony, Tony Day writes: > More like a terrible example. Here's a more complicated one out in the > wild (from https://github.com/renard/o-blog) - templating html creation. > > https://gist.github.com/4333546 > > I imagine patches would be welcome :) Well... spare you the sweat, because I'm not even sure we'd like such a patch :) Indentation is a visual clue about the structure of the code -- if you lose the structure (like in the HTML scattered snippets of the link above), the visual clue will does not help anymore... imagine if you are deep in the HTML AST and have to indent by 20 whitespaces? That would not help at all -- instead, you want the snippet to be read as if it was on the top of the AST. Anyway, perhaps that's just me... -- Bastien