emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: emacs-orgmode@gnu.org
Subject: Re: babel detangling visits a large number of files
Date: Sun, 10 Mar 2019 18:30:16 +0100	[thread overview]
Message-ID: <87k1h6sklz.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87pnr4kqj7.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Wed, 06 Mar 2019 14:48:12 +0000")

Hello,

Eric S Fraga <esflists@gmail.com> writes:

> Hello,
>
> motivated by having just watched this video,
>
> https://www.youtube.com/watch?time_continue=479&v=BLomb52wjvE
>
> I decided to play around a bit with detangling.
>
> When I try, it takes some time to get to the original src block.  Even
> though the comment entry before the code looks very reasonable, e.g.:
>
> #+begin_src julia
>   # [[file:~/s/research/strawberry/src/fresa.org::modulestart][modulestart]]
>   module Fresa
>     [... code elided ...]
>   end
>   # modulestart ends here
> #+end_src
>
> invoking org-babel-tangle-jump-to-org proceeds to visit a large number
> of files (I only know because many of them require accepting some local
> file variable settings when the files are visited) and org further
> complains about a large number of multiply defined IDs.
>
> Given that the detangling information in the comment has the file
> explicitly stated, why should the detangling procedure care about IDs
> and why does it need to visit so many files?  Have I configured
> something wrongly?

I think I fixed it in master branch. Could you test it ?

Beware, master branch also include the link syntax change.

Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2019-03-10 17:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-06 14:48 babel detangling visits a large number of files Eric S Fraga
2019-03-10 17:30 ` Nicolas Goaziou [this message]
2019-03-11  9:37   ` Eric S Fraga

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=87k1h6sklz.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    /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).