From: Immanuel Litzroth <immanuel.litzroth@gmail.com>
To: Stephen Eglen <sje30@cam.ac.uk>
Cc: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: Moving to a literate file for .emacs
Date: Mon, 4 Jul 2022 19:49:31 +0200 [thread overview]
Message-ID: <CAM1nAcy2rAYmQPTZBbmDjgUnyVMqXnLmDB9z8xf4atskDA38HQ@mail.gmail.com> (raw)
In-Reply-To: <m2fsjh56ms.fsf@blur.lan>
It's possible to let tangling generate comments that will link back to the
literate file where you defined the function.
https://orgmode.org/manual/Extracting-Source-Code.html
See the comment header arg.
Then you could advise the relevant functions that do emacs function lookup
to check whether there's such a "link comment" near the definition and jump
to that instead.
All this is rather hackish and I stopped doing my init files in literate org.
Immanuel
On Mon, Jul 4, 2022 at 4:07 PM Stephen Eglen <sje30@cam.ac.uk> wrote:
>
> I see many users are switching to using a 'literate programming'
> approach to tangling their .emacs file from an org file.
>
> Has anyone solved the following problem though? If I have a file called
> config.org containing:
>
> * test
>
> #+begin_src emacs-lisp
> (defun quick-test ()
> "interactive"
> (* 3 9)
> )
> #+end_src
>
>
> and then in my .emacs file I do:
>
> (org-babel-load-file "~/config.org")
>
> quick-test is indeed defined, but when I do C-c f RET quick-test RET it
> takes me to config.el (a tangled file, suitable for computers, not
> humans), rather than config.org. Is it possible instead to get the
> editor to jump to the definition in config.org?
>
> Stephen
>
>
--
-- A man must either resolve to point out nothing new or to become a
slave to defend it. -- Sir Isaac Newton
next prev parent reply other threads:[~2022-07-04 17:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 13:44 Moving to a literate file for .emacs Stephen Eglen
2022-07-04 17:49 ` Immanuel Litzroth [this message]
2022-07-05 2:28 ` Samuel Banya
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=CAM1nAcy2rAYmQPTZBbmDjgUnyVMqXnLmDB9z8xf4atskDA38HQ@mail.gmail.com \
--to=immanuel.litzroth@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=sje30@cam.ac.uk \
/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).