Nicolas Goaziou <m...@nicolasgoaziou.fr> writes: > Thomas S. Dye <t...@tsdye.com> writes: > >> Nicolas Goaziou <m...@nicolasgoaziou.fr> writes: >> >>> The full proposal was at >>> <http://permalink.gmane.org/gmane.emacs.orgmode/97468> but it didn't get >>> much positive feedback. Therefore I suggested a simplified version, with >>> a single author. >> >> In my case, the lack of positive feedback was "too much org, too little >> time". >> >> The original version, which includes the author Fabrice mentioned, seems >> superior to me. It potentially eases collaboration and also configuring >> alternate versions of the same document. >> >> I'm not clear about affiliated keyword for source code blocks. Would >> tangling honor #+OPTIONS: <at> :student1? > > The limitation is that you can only replace the code block as a whole, > so with > > #+annotate: bugfix > #+name: bikeshed > #+begin_src emacs-lisp > (paint 'bikeshed blue) > #+end_src > > * Annotations > > [@:bugfig:me] > # You're clearly wrong > #+begin_src emacs-lisp > (pain 'bikeshed green) > #+end_src > > when using > > #+OPTIONS: @:me > > body becomes > > #+name: bikeshed > #+begin_src emacs-lisp > (paint 'bikeshed green) > #+end_src
And also, #+name: baz #+begin_src emacs-lisp :noweb yes (some code) <<bikeshed>> (other code) #+end_src so the various :noweb options, including evaluation of baz in the Org mode buffer, honor #+OPTIONS: @:me? All the best, Tom -- Thomas S. Dye http://www.tsdye.com
