From: Brad Knotwell <bknotwell@yahoo.com>
To: Grant Rettke <gcr@wisdomandwonder.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: org-babel-detangle issue on 9.1.14
Date: Thu, 4 Oct 2018 15:51:43 +0000 (UTC) [thread overview]
Message-ID: <213080806.4531977.1538668303406@mail.yahoo.com> (raw)
In-Reply-To: <CAAjq1mdfSAP6aYfimtf1GUCBu687y2wgokPPdMU2rR6eovbaSw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2426 bytes --]
Thanks for the response. At a minimum, I'd recommend changing the error message from "Not in a source block" to something more descriptive as most people's initial response will be, "uhhh, but it looks like I am."
Ideally, an additional comment marker would delineate the source block from the meta-programmed variables to allow the edited source code's verbatim replacement. Or it might make sense to have a setting that separates the tangled source file from the meta programmed variables. Using your example above, it could tangle to something like the following:
#!/bin/sh
# [[file:~/tmp/test.org::org_gcr_2018-10-04T08-35-43-05-00_cosmicality_CCEACAA2-A6B3-4FDD-9259-7F633316F0CE][org_gcr_2018-10-04T08-35-43-05-00_cosmicality_CCEACAA2-A6B3-4FDD-9259-7F633316F0CE]]. ./noideahowtonamethesegenerically.sh # the naming seems tricky to me
echo $x# org_gcr_2018-10-04T08-35-43-05-00_cosmicality_CCEACAA2-A6B3-4FDD-9259-7F633316F0CE
ends here
If babel was starting anew, I'd prefer that as it seems cleaner than adding another comment (assumption: majority of languages have an include-like facility of some sort). Given the number of languages currently supported, the additional comment delimiters seem less disruptive.
--Brad
On Thursday, October 4, 2018, 8:19:30 AM PDT, Grant Rettke <gcr@wisdomandwonder.com> wrote:
On Thu, Oct 4, 2018 at 2:09 AM Brad Knotwell <bknotwell@yahoo.com> wrote:
> I've been playing with org-babel-detangle and I've noticed something that's either a bug or a limitation. It's confusing enough that
> it's worth writing down if it's expected. Basically, it doesn't work if there are variables defined in the begin_src header. I've
> attached an example below. The first one won't detangle and the last two will.
That is expected behavior. Org can only detangle the content of source
blocks. It can't deduce how that
source code got in there.
Maybe this example says it better:
#+begin_src sh sh :tangle hw.sh :var x=(random) :shebang #!/bin/sh
:comments link
echo $x
#+end_src
Tangles to
#!/bin/sh
# [[file:~/tmp/test.org::org_gcr_2018-10-04T08-35-43-05-00_cosmicality_CCEACAA2-A6B3-4FDD-9259-7F633316F0CE][org_gcr_2018-10-04T08-35-43-05-00_cosmicality_CCEACAA2-A6B3-4FDD-9259-7F633316F0CE]]
x='422131055910453451'
echo $x
# org_gcr_2018-10-04T08-35-43-05-00_cosmicality_CCEACAA2-A6B3-4FDD-9259-7F633316F0CE
ends here
[-- Attachment #2: Type: text/html, Size: 4085 bytes --]
next prev parent reply other threads:[~2018-10-04 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <833272723.4259898.1538636915102.ref@mail.yahoo.com>
2018-10-04 7:08 ` org-babel-detangle issue on 9.1.14 Brad Knotwell
2018-10-04 15:19 ` Grant Rettke
2018-10-04 15:51 ` Brad Knotwell [this message]
2018-10-05 20:06 ` Grant Rettke
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=213080806.4531977.1538668303406@mail.yahoo.com \
--to=bknotwell@yahoo.com \
--cc=emacs-orgmode@gnu.org \
--cc=gcr@wisdomandwonder.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 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).