From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: ox-koma-letter: how to use @@LaTeX:@@ specific commands in #+ directives Date: Thu, 18 Jun 2015 16:07:01 +0200 Message-ID: <87616l6rga.fsf@selenimh.access.network> References: <87y4jimeai.fsf@delle7240.chemeng.ucl.ac.uk> <87bngexeyv.fsf@gmx.us> <87twu66lh1.fsf@selenimh.access.network> <87616lcufl.fsf@delle7240.chemeng.ucl.ac.uk> <87lhfh8kto.fsf@gmx.us> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33607) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z5aRi-0000yd-TT for emacs-orgmode@gnu.org; Thu, 18 Jun 2015 10:05:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z5aRh-0007i1-LJ for emacs-orgmode@gnu.org; Thu, 18 Jun 2015 10:05:34 -0400 Received: from relay3-d.mail.gandi.net ([2001:4b98:c:538::195]:58270) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z5aRh-0007hc-FS for emacs-orgmode@gnu.org; Thu, 18 Jun 2015 10:05:33 -0400 In-Reply-To: <87lhfh8kto.fsf@gmx.us> (rasmus@gmx.us's message of "Thu, 18 Jun 2015 10:47:15 +0200") 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: Rasmus Cc: emacs-orgmode@gnu.org Hello, Rasmus writes: > Nicolas: are there any of the keywords in the patch that shouldn't be > parsed? I don't think so. Notwithstanding AUTHOR, which clearly is an overlook (ox.el parses it), I wonder if it is a net gain, tho. In my experience, these values are mostly constituted of LaTeX code anyway (e.g., \vspace and \hspace in signature) and this change will not make them simpler. > Also, I left out FROM_ADDRESS as I remember it interprets newlines and I > don't have time ATM to properly check if this depends on the newline > behavior. Indeed, `parse' treats newline characters as spaces, so it is not a replacement for `newline'. Note that SIGNATURE has the same problem. Regards, -- Nicolas Goaziou