From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Schulte Subject: Re: string joining accumulated noweb references Date: Tue, 24 Jan 2012 00:04:37 -0700 Message-ID: <87obttk2d3.fsf@gmx.com> References: <87aa5eqhxz.fsf@gmx.com> <87k44hampv.fsf@tomsdiner.org> <87ehupq0g7.fsf_-_@gmx.com> <87sjj5ipn4.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:52232) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RpaR4-0003Du-AO for emacs-orgmode@gnu.org; Tue, 24 Jan 2012 02:04:55 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RpaR1-00034w-Ph for emacs-orgmode@gnu.org; Tue, 24 Jan 2012 02:04:54 -0500 Received: from mailout-us.gmx.com ([74.208.5.67]:55039) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1RpaR1-000328-Gy for emacs-orgmode@gnu.org; Tue, 24 Jan 2012 02:04:51 -0500 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Achim Gratz Cc: emacs-orgmode@gnu.org Achim Gratz writes: > Eric Schulte writes: >> I just pushed up a new customization variable named >> `org-babel-noweb-separator' which is used to join multiple accumulated >> noweb references like the above. The value defaults to a newline giving >> the same behavior resulting from your patch but can be set to any >> string. > > Now, lets say I'd want to accumulate one set of noweb references with > one separator and another set with a different one, maybe even in the > same document. How'd I do that? > Not possible in the same document, although on a document-by-document basis I would recommend the use of file local variables. > > Also, using a customization variable for the purpose of changing the > semantics of documents is generally fraught with peril: if someone does > customize this variable, their documents will break in subtle ways for > somebody with a different or no customization. I suggest that such > changes should always be visible in the source document itself. > That is a very good point. I had originally started to implement this parameter using a header argument, but then decided that it didn't make sense to implement a multi-block parameter using a header argument. Now that you mention this however I do agree that a customization parameter is even less appropriate. Given that header arguments may be set on the file and subtree level, I suppose they do offer the range of application appropriate for this sort of parameter, and they are more likely (though not guaranteed) to have their value present in the buffer. I've just pushed up a change converting the `org-babel-noweb-separator' customization variable to the :noweb-sep header argument. Thanks, > > > Regards, > Achim. -- Eric Schulte http://cs.unm.edu/~eschulte/