From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Kitchin Subject: Re: map function definitions to org src blocks? Date: Thu, 8 Nov 2018 18:02:18 -0500 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000b2f2c3057a2f3ac5" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39866) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gKtX5-0002yu-OV for emacs-orgmode@gnu.org; Thu, 08 Nov 2018 18:16:16 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gKtK7-0001RZ-QE for emacs-orgmode@gnu.org; Thu, 08 Nov 2018 18:02:52 -0500 Received: from mail-wr1-x436.google.com ([2a00:1450:4864:20::436]:34083) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gKtK5-0001IS-P4 for emacs-orgmode@gnu.org; Thu, 08 Nov 2018 18:02:50 -0500 Received: by mail-wr1-x436.google.com with SMTP id j26-v6so23024296wre.1 for ; Thu, 08 Nov 2018 15:02:31 -0800 (PST) In-Reply-To: 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" To: Matt Price Cc: Org Mode --000000000000b2f2c3057a2f3ac5 Content-Type: text/plain; charset="UTF-8" I wrote something kind of like this at https://github.com/jkitchin/scimax/blob/master/scimax-literate-programming.el It might solve a different problem related to navigating code embedded in org files. I don't think it works on describe-function. That would be an interesting addition perhaps. I guess though that describe-function would go to the elisp code. I never figured out how to get links in the tangled code to jump back to the org file though. On Thu, Nov 8, 2018 at 5:39 PM Matt Price wrote: > I feel like I saw someone do this but can't find it in my notes. When > tangling code to elisp, is it possible to point ~describe-function~ to the > original org-mode source (or at least the src block) as the "source code" > for the function, rather than the resultant .e file produced by > org-babel-tangle? Seems like this would make a whole lot of things > significantly easier when writing emacs inits, for instnace. > -- John ----------------------------------- Professor John Kitchin Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 @johnkitchin http://kitchingroup.cheme.cmu.edu --000000000000b2f2c3057a2f3ac5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I wrote something kind of like this at=C2=A0

It might solve a different problem related to navigating code embedded in = org files.

I don't think it works on describe-function. That would be an inter= esting addition perhaps. I guess though that describe-function would go to = the elisp code. I never figured out how to get links in the tangled code to= jump back to the org file though.=C2=A0

On Thu, Nov 8, 2018 at 5:39 PM Matt Price <moptop99@gmail.com> wrote:
I feel like I saw someone do th= is but can't find it in my notes. When tangling code to elisp, is it po= ssible to point ~describe-function~ to the original org-mode source (or at = least the src block) as the "source code" for the function, rathe= r than the resultant .e file produced by org-babel-tangle? Seems like this = would make a whole lot of things significantly easier when writing emacs in= its, for instnace. =C2=A0
--
J= ohn

-----------------------------------
Professor John Kitchin=C2= =A0
Doherty Hall A207F
Department of Chemical Engineering
Carnegie= Mellon University
Pittsburgh, PA 15213
412-268-7803
=
--000000000000b2f2c3057a2f3ac5--