emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Price <moptop99@gmail.com>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: map function definitions to org src blocks?
Date: Thu, 8 Nov 2018 22:22:36 -0500	[thread overview]
Message-ID: <CAN_Dec_j33nUOGJ4oHONezd4oyzhwP8SjGpFn0ihC+SvpMi9+w@mail.gmail.com> (raw)
In-Reply-To: <CAJ51ETohAcXcGeGR04zotZEtFHLvAT20mP=LuLUrms8Odk6Lhw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1582 bytes --]

THanks John. I guess I should always just start my search for "something
cool I saw" in scimax...

Yes, thisis pretty great. I havebeen using ~helpful~ which hasa nice
interface for some extra functions, but these functions do most of what I
felt was missing.

On Thu, Nov 8, 2018 at 6:02 PM John Kitchin <jkitchin@andrew.cmu.edu> wrote:

> 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 <moptop99@gmail.com> 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
>
>

[-- Attachment #2: Type: text/html, Size: 2623 bytes --]

  reply	other threads:[~2018-11-09  3:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08 22:27 map function definitions to org src blocks? Matt Price
2018-11-08 23:02 ` John Kitchin
2018-11-09  3:22   ` Matt Price [this message]
2018-11-09 14:40     ` John Kitchin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAN_Dec_j33nUOGJ4oHONezd4oyzhwP8SjGpFn0ihC+SvpMi9+w@mail.gmail.com \
    --to=moptop99@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jkitchin@andrew.cmu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).