Re: [PATCH] Allow tangling to a list of files

[Jacopo De Simoi]

Hi Greg, 

thanks for your comments!

On Tuesday, July 6, 2021 12:43:54 AM EDT Greg Minshall wrote:
> hi, Jacopo,
> 
> i'm not convinced this is needed over and above your old "solution" of
> using <<noweb>> witn N-different source blocks, each :tangle'ing to a
> different file.

To be honest I never quite managed to get it work... =) 

My point here is to be able to have one org file tangle'ing to several, 
slightly different outputs.  Ideally I want to use one readable literate config 
for all my machines; the config can then be published (or exported) to html

Say I want to create an org file to tangle .tmux.conf (or .zshrc) for different 
machines; then most of the conf file would be the same (and each such block 
would be tangled to all files) whereas some specifics could be tangled to 
corresponding files only (e.g. ALIASes or EDITORs) 

Even if a solution using noweb could work, I find being able to tangle to a 
list of files more readable and elegant. Especially when exporting the org in 
an external format, I think the noweb solution would look like a hack, whereas 
a solution with tangle-to-list would be much easier to parse. 

> 
> but, i'm curious -- in the example you sent, did you miss a ":tangle" on
> the "#+begin_src" line?

Yikes! of course I did! Good catch.
> 
> > #+begin_src sh '("filename1" "filename2")
> > #my script
> > #+end_src
> 

Best,
 Jacopo