Re: org-babel-detangle issue on 9.1.14

[Grant Rettke <gcr@wisdomandwonder.com>]

On Thu, Oct 4, 2018 at 10:53 AM Brad Knotwell <bknotwell@yahoo.com> wrote:
> 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."

Consider submitting your suggestion as a patch so it is super easy to
know what change you are suggesting.

If you never submitted one before I am glad to help.

> 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

One way is that you can keep the values in an external file and load
it before each source block in the preamble code?

I'm thinking pretty simply but depending on what you wan to do here
there might be an easy solution.