From mboxrd@z Thu Jan 1 00:00:00 1970 From: Achim Gratz Subject: Re: [ox-publish] handling of white space in arguments of macros, named arguments? Date: Thu, 28 Mar 2013 07:59:38 +0100 Message-ID: References: <31F8FCDD-923C-402B-AD87-FEB6C8F84B12@nf.mpg.de> <87d2ukg66d.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:37535) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UL6nv-0003sT-8u for emacs-orgmode@gnu.org; Thu, 28 Mar 2013 02:59:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UL6nu-0004MF-97 for emacs-orgmode@gnu.org; Thu, 28 Mar 2013 02:59:19 -0400 Received: from plane.gmane.org ([80.91.229.3]:60520) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UL6nu-0004M3-2I for emacs-orgmode@gnu.org; Thu, 28 Mar 2013 02:59:18 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UL6o9-0002iH-OO for emacs-orgmode@gnu.org; Thu, 28 Mar 2013 07:59:33 +0100 Received: from p5b14db4d.dip.t-dialin.net ([91.20.219.77]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 28 Mar 2013 07:59:33 +0100 Received: from Stromeko by p5b14db4d.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 28 Mar 2013 07:59:33 +0100 In-Reply-To: <87d2ukg66d.fsf@gmail.com> 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: emacs-orgmode@gnu.org Am 27.03.2013 17:26, schrieb Nicolas Goaziou: > I think all newline characters should be replaced with a whitespace > character in macro arguments. Indeed, macro templates are only one line > long but unwanted "\n" could be inserted by paragraph filling in > arguments. I'm not sure about that, it would mean that there'd need to be additional syntax to insert linebreaks. > I also don't mind trimming arguments again, provided this is added as an > explicit behaviour and there is no opposition to it. How about making trimming explicit during the expansion of macro arguments? It seems that there are a few possibilities of what trimming could mean, so this would be an opportunity to allow them all (n is the argument number): $:n - remove whitespace and linebreaks before argument $.n - remove whitespace and linebreaks after argument $n - same as $:.n $+n - replace whitespace and linebreaks inside arguments with a single space $*n - same as $:+.n $~n - literal argument (no trimming) Regards, -- Achim. (on the road :-)