From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Short Subject: Re: [babel]: Some feedback after the first week usage Date: Thu, 5 Nov 2009 22:48:03 +0000 (UTC) Message-ID: References: <200911051727.44814.torsten.wagner@googlemail.com> <87639o287h.fsf@stats.ox.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N6B8J-0003wm-RQ for emacs-orgmode@gnu.org; Thu, 05 Nov 2009 17:48:47 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N6B8E-0003qC-PM for emacs-orgmode@gnu.org; Thu, 05 Nov 2009 17:48:47 -0500 Received: from [199.232.76.173] (port=55371 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N6B8E-0003pw-Eu for emacs-orgmode@gnu.org; Thu, 05 Nov 2009 17:48:42 -0500 Received: from lo.gmane.org ([80.91.229.12]:44194) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1N6B8D-000410-OL for emacs-orgmode@gnu.org; Thu, 05 Nov 2009 17:48:42 -0500 Received: from list by lo.gmane.org with local (Exim 4.50) id 1N6B87-0000oh-GT for emacs-orgmode@gnu.org; Thu, 05 Nov 2009 23:48:35 +0100 Received: from pool-71-245-142-189.albyny.east.verizon.net ([71.245.142.189]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 05 Nov 2009 23:48:35 +0100 Received: from tshort by pool-71-245-142-189.albyny.east.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 05 Nov 2009 23:48:35 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Dan Davison stats.ox.ac.uk> writes: > > Torsten Wagner gmail.com> writes: > > <...> > > 4. Is there a way to see all source code blocks of a single session tangled > > together in a single buffer and changes in this buffer will be placed back after > > leaving into the individual blocks again > > It sounds nice, but very challenging. Would such a mechanism be robust > to very disruptive edits in the tangled code buffer (e.g. moving large > blocks of text around)? Would it be able to meaningfully maintain a > mapping between buffer regions and code blocks? You'd want to start off > by looking at the code in org-src.el to see whether you thought it could > be extended. One way this could be implemented is with an indirect buffer. In the indirect buffer, you could use an overlay to hide all the org parts and just leave the code parts visible. You're not really tangling, just hiding the non-code stuff. You might even be able to operate the indirect buffer in ess-mode or python mode if you wanted. - Tom