n org files, with all the potential for name
collisions and the like that that implies. One could avoid such problems by
adding some kind of prefix to the block names in the included file (maybe
"common/" or "xyzzy-"). (Some kind of automatic prefixing on inclusion might be
cool.)
--Kevin M. Stout
On 2021-02-15 14:18, Rodrigo Morales wrote:
> 1. Do you use long names?
Usually. Suppose you were doing a bit of genetic programming. You might have a
function that computes the next generation from the current one. You could
write the following snippet that looks suspiciously like pseudocode:
age :noweb-ref "this is a cool way to do something"
stuff
#+END_SRC
especially as a project grows.
Perhaps we could have a variation on #+NAME that doesn't need to be unique?
Maybe something like #+NOREF, to evoke :noweb-ref? Or #+NONAME?
Sincerely,
Kevin M. Stout
change org-babel-tangle's accumulation behavior for duplicate
#+NAME's. It's handy, and users of other literate programming tools will find it
familiar. Also, #+NAME is a nicer per-block syntax than :noweb-ref.
Sincerely,
Kevin M. Stout