From: Nick Dokos <nicholas.dokos@hp.com>
Cc: "emacs-orgmode@gnu.org List" <emacs-orgmode@gnu.org>,
Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: New exporter macro question
Date: Mon, 11 Feb 2013 11:31:23 -0500 [thread overview]
Message-ID: <419.1360600283@alphaville> (raw)
In-Reply-To: Message from Nick Dokos <nicholas.dokos@hp.com> of "Mon, 11 Feb 2013 09:43:12 EST." <31732.1360593792@alphaville>
Nick Dokos <nicholas.dokos@hp.com> wrote:
> Carsten Dominik <carsten.dominik@gmail.com> wrote:
>
> > OK, I see, this seems to be because the "\n" is no longer
> > interpreted as a newline character upon macro expansion, so the
> > entire text ends up in the ATTR_HTML line and is treated as a
> > comment.
>
> It seems to be coming from deep with emacs: if I create a buffer
> with
>
> x y z \ x y z
>
> and evaluate (with point somewhere on that line)
>
> (buffer-substring-no-properties (point-at-bol) (point-at-eol))
>
> I get "x y z \\ x y z", so the backslash is escaped willy-nilly.
>
> This happens in org-element-keyword-parser. I don't know if the
> macro expansion would replace \n with a newline absent the extra
> backslash, but I'm sure that its presence does not help any.
>
Even if I delete the extra backslash from the value of the macro
in org-macro-initialize-templates, the regexp fails to properly
match:
,----
| ;; Install buffer-local macros.
| (org-with-wide-buffer
| (goto-char (point-min))
| (while (re-search-forward "^[ \t]*#\\+MACRO:" nil t)
| (let ((element (org-element-at-point)))
| (when (eq (org-element-type element) 'keyword)
| (let ((value (org-element-property :value element)))
| (when (string-match "^\\(.*?\\)\\(?:\\s-+\\(.*\\)\\)?\\s-*$" value)
| (funcall set-template
| (cons (match-string 1 value)
| (or (match-string 2 value) "")))))))))
`----
OTOH, if I modify the cell argument inside set-template[fn:1] to get rid of
the extra backslash, the macro expansion happened as expected.
Nick
Footnotes:
[fn:1] This is obviously a gross hack, only meant as a debugging aid.
In fact, I didn't even code it up: I just stepped through the
thing with edebug and slammed the modified value into the cell
argument.
next prev parent reply other threads:[~2013-02-11 16:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 12:48 New exporter macro question Carsten Dominik
2013-02-11 13:45 ` Carsten Dominik
2013-02-11 14:43 ` Nick Dokos
2013-02-11 16:31 ` Nick Dokos [this message]
2013-02-11 21:37 ` Nicolas Goaziou
2013-02-12 6:23 ` Carsten Dominik
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=419.1360600283@alphaville \
--to=nicholas.dokos@hp.com \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).