From mboxrd@z Thu Jan 1 00:00:00 1970 From: Seth Burleigh Subject: Re: [babel] Painless integration of source blocks with language Date: Thu, 13 Jan 2011 17:44:19 -0600 Message-ID: References: <87lj2ukfia.fsf@gmail.com> <87k4icegwl.fsf@ucl.ac.uk> <87wrmbwdsm.fsf@gmail.com> <87aaj5tbgl.fsf@ucl.ac.uk> <87bp3ka458.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1257774472==" Return-path: Received: from [140.186.70.92] (port=56632 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PdWq6-000579-4e for emacs-orgmode@gnu.org; Thu, 13 Jan 2011 18:44:23 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PdWq5-0002Lx-0w for emacs-orgmode@gnu.org; Thu, 13 Jan 2011 18:44:22 -0500 Received: from mail-iy0-f169.google.com ([209.85.210.169]:47260) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PdWq4-0002Lo-SZ for emacs-orgmode@gnu.org; Thu, 13 Jan 2011 18:44:20 -0500 Received: by iyj17 with SMTP id 17so2249049iyj.0 for ; Thu, 13 Jan 2011 15:44:19 -0800 (PST) In-Reply-To: <87bp3ka458.fsf@gmail.com> 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: Eric Schulte Cc: emacs-orgmode@gnu.org --===============1257774472== Content-Type: multipart/alternative; boundary=001485e7e9487f697b0499c2e5ca --001485e7e9487f697b0499c2e5ca Content-Type: text/plain; charset=ISO-8859-1 >As for how to trace back through noweb links, the best option seem to be >using the existing jump function to navigate from raw source to the >embedded block, keeping track of the point's offset form the beginning >of the block, then using `org-babel-expand-src-block' to expand the body >of the embedded code block marking noweb references with text properties >as they are inserted into the expanding body, and then using the point >offset to place the point into the appropriate noweb reference. This >process could then recurse on the embedded noweb code block until it >ends up in a non-noweb portion of an expanded code block body. If you dont have any comment anchors in the text, how would you know which noweb block you are in? If your org file and raw files are synched, then you could, but if they become unsynched, which is the way it should be (change raw code until done, then detangle to org), i dont exactly see how you can do it. The only option which allows someone to change the raw text file is to use comment anchors - or you could save marks in a separate file, but this wouldn't allow for offline editing unless you open it with a program that understands this format. With the comment method, you get the raw file advantage, plus emacs can hide these comments if one makes a minor mode to do so - a win win situation, i think, except for the aforementioned shortcomings. --001485e7e9487f697b0499c2e5ca Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 
>As for how to trace back through noweb links, th=
e best option seem to be
>using the existing jump function to navigate from raw source to the
>embedded block, keeping track of the point's offset form the beginn=
ing
>of the block, then using `org-babel-expand-src-block' to expand the=
 body
>of the embedded code block marking noweb references with text propertie=
s
>as they are inserted into the expanding body, and then using the point
>offset to place the point into the appropriate noweb reference.  This
>process could then recurse on the embedded noweb code block until it
>ends up in a non-noweb portion of an expanded code block body.
If you dont have any comment anchors in the text, how would you know wh= ich =A0noweb block you are in? If your org file and raw files are synched, = then you could, but if they become unsynched, which is the way it should be= (change raw code until done, then detangle to org), i dont exactly see how= you can do it.=A0

The only option which allows someone to change the raw text = file is to use comment anchors - or you could save marks in a separate file= , but this wouldn't =A0allow for offline editing unless you open it wit= h a program that understands this format. With the comment method, you get = the raw file advantage, plus emacs can hide these comments if one makes a m= inor mode to do so - a win win situation, i think, except for the aforement= ioned shortcomings.=A0


--001485e7e9487f697b0499c2e5ca-- --===============1257774472== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode --===============1257774472==--