On 10 November 2016 at 01:19, Charles C. Berry wrote:
> when developing stuff like this `:wrap src org' will capture it and protect
> against messing up the rest of your *.org file.
My goodness, you think of everything! Thanks very much Charles.
--
Phil Hudson http://hudson-it
On Wed, 9 Nov 2016, Philip Hudson wrote:
On 9 November 2016 at 21:41, Charles C. Berry wrote:
The org src block is just a container. Its body is a src block template that
gets copied into the variable `tmpl', which if filled and placed in file can
be tangled.
That makes sense, but it seems t
On 9 November 2016 at 21:41, Charles C. Berry wrote:
> The org src block is just a container. Its body is a src block template that
> gets copied into the variable `tmpl', which if filled and placed in file can
> be tangled.
That makes sense, but it seems to conflict with what you illustrate:
#+
On Wed, 9 Nov 2016, Philip Hudson wrote:
On 9 November 2016 at 17:54, Charles C. Berry wrote:
On Tue, 8 Nov 2016, Philip Hudson wrote:
[snip]
How do you do "looping" flow control?
For context, what I'm trying to write is a single Org file from which
I can tangle out a number of =~/.ssh/con
On 9 November 2016 at 17:54, Charles C. Berry wrote:
> On Tue, 8 Nov 2016, Philip Hudson wrote:
>
> [snip]
>>
>> How do you do "looping" flow control?
>>
>> For context, what I'm trying to write is a single Org file from which
>> I can tangle out a number of =~/.ssh/config= files, one for each of
On Tue, 8 Nov 2016, Philip Hudson wrote:
[snip]
How do you do "looping" flow control?
For context, what I'm trying to write is a single Org file from which
I can tangle out a number of =~/.ssh/config= files, one for each of
several hosts on a LAN. Within this file I need to repeatedly place a
