From: Rainer M Krug <Rainer@krugs.de>
To: emacs-orgmode@gnu.org
Subject: Re: [BUG][babel] Tangling into directories does not add directories to org file
Date: Thu, 09 Oct 2014 14:37:08 +0200 [thread overview]
Message-ID: <m2vbntto5n.fsf@krugs.de> (raw)
In-Reply-To: <m2tx3evgs7.fsf@krugs.de> (Rainer M. Krug's message of "Wed, 08 Oct 2014 15:21:12 +0200")
I'd like to ping this as I think it
is an important bug. It e.g. make debugging of R packages, whose source
is in org, more difficult, (the .R files are tangled into ./R/) as ess
does not find the source of the R code in R as it uses the links in the
comments to find the org file.
Temporary solution: I created a link to the org file in the ./R directory.
Cheers,
Rainer
Rainer M Krug <Rainer@krugs.de> writes:
> When in the tangling taerget a directory is specified, this is not
> reflected in the comments in the tangled file when comments are set to
> include links:
>
> ,----
> | * `link' The code block is wrapped in comments which contain
> | pointers back to the original Org file from which the code was
> | tangled.
> `----
>
> In the org file =prodMixStands.org=:
>
> ,----
> | :PROPERTIES:
> | :header-args+: :tangle ./R/update.cache.R
> | :END:
> | #+begin_src R
> | test
> | #+end_src
> `----
>
> results in the file =update.cache.R= in a link to the file
> =prodMixStands.org= and not =./../prodMixstands.org=:
>
> ,----
> | ## [[file:prodMixStands.org::*Begin][Begin:1]]
> `----
>
> This is particularly bad when using ess and developer mode to develop a
> package.
>
> Cheers,
>
> Rainer
--
Rainer M. Krug
email: Rainer<at>krugs<dot>de
PGP: 0x0F52F982
next prev parent reply other threads:[~2014-10-09 12:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 13:21 [BUG][babel] Tangling into directories does not add directories to org file Rainer M Krug
2014-10-09 12:37 ` Rainer M Krug [this message]
2014-10-10 2:13 ` Grant Rettke
2014-10-10 8:24 ` Rainer M Krug
2014-10-10 14:41 ` Grant Rettke
2014-10-10 3:55 ` Aaron Ecay
2014-10-10 8:45 ` Rainer M Krug
2014-10-10 16:34 ` Aaron Ecay
2014-10-10 16:50 ` Thorsten Jolitz
2014-10-10 18:37 ` Grant Rettke
2014-10-10 16:55 ` Aaron Ecay
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=m2vbntto5n.fsf@krugs.de \
--to=rainer@krugs.de \
--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).