emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: ox-koma-letter: how to use @@LaTeX:@@ specific commands in #+ directives
Date: Thu, 18 Jun 2015 16:07:01 +0200	[thread overview]
Message-ID: <87616l6rga.fsf@selenimh.access.network> (raw)
In-Reply-To: <87lhfh8kto.fsf@gmx.us> (rasmus@gmx.us's message of "Thu, 18 Jun 2015 10:47:15 +0200")

Hello,

Rasmus <rasmus@gmx.us> 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

      parent reply	other threads:[~2015-06-18 14:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17 17:32 ox-koma-letter: how to use @@LaTeX:@@ specific commands in #+ directives Eric S Fraga
2015-06-17 20:22 ` Rasmus
2015-06-17 22:03   ` Nicolas Goaziou
2015-06-17 22:55     ` Rasmus
2015-06-18  8:06     ` Eric S Fraga
2015-06-18  8:47       ` Rasmus
2015-06-18  9:09         ` Eric S Fraga
2015-06-18 21:01           ` Rasmus
2015-06-19 14:24             ` Eric S Fraga
2015-06-19 15:28             ` Eric S Fraga
2015-06-18 14:07         ` Nicolas Goaziou [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87616l6rga.fsf@selenimh.access.network \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=rasmus@gmx.us \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).