all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Matt Price <moptop99@gmail.com>
Cc: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: map function definitions to org src blocks?
Date: Fri, 9 Nov 2018 09:40:37 -0500	[thread overview]
Message-ID: <CAJ51ETpjno2HU9wFKCHamwYhic8dq9RF9OudHv7-Nezu5hP9dA@mail.gmail.com> (raw)
In-Reply-To: <CAN_Dec_j33nUOGJ4oHONezd4oyzhwP8SjGpFn0ihC+SvpMi9+w@mail.gmail.com>

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

It looks like it is possible to get describe-func to point to an org-file.
Suppose I have a file /Users/jkitchin/vc/journal/2018/11/09/2018-11-09.org
that has src blocks that tangle to
/Users/jkitchin/vc/journal/2018/11/09/test.el. When test.el is loaded, it
adds a bunch of stuff to the variable load-history that describe-function
can use to get information. For example:

#+BEGIN_SRC emacs-lisp
(assoc "/Users/jkitchin/vc/journal/2018/11/09/test.el" load-history)
#+END_SRC

#+RESULTS:
: (/Users/jkitchin/vc/journal/2018/11/09/test.el (defun . some-func))

One solution is to just change the file name in load-history like this.

#+BEGIN_SRC emacs-lisp
(setf (car (assoc "/Users/jkitchin/vc/journal/2018/11/09/test.el"
load-history)) "/Users/jkitchin/vc/journal/2018/11/09/2018-11-09.org")
#+END_SRC
John

Something like this could be handled in an :after advice for example.

This is only lightly tested... I don't know if it has other implications.

-----------------------------------
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



On Thu, Nov 8, 2018 at 10:22 PM Matt Price <moptop99@gmail.com> wrote:

> 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: 4848 bytes --]

      reply	other threads:[~2018-11-09 14:40 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
2018-11-09 14:40     ` John Kitchin [this message]

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

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

  git send-email \
    --in-reply-to=CAJ51ETpjno2HU9wFKCHamwYhic8dq9RF9OudHv7-Nezu5hP9dA@mail.gmail.com \
    --to=jkitchin@andrew.cmu.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=moptop99@gmail.com \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.