From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: new exporter
Date: Sun, 01 Jul 2012 18:33:05 +0200 [thread overview]
Message-ID: <87r4sv5tmm.fsf@Rainer.invalid> (raw)
In-Reply-To: 87fw9d1eif.fsf@gmail.com
Nicolas Goaziou writes:
> I will look more carefully at the `org-export-with-current-buffer-copy'
> macro, but, since I cannot reproduce the compilation error it may be
> hard to find the mistake.
After some consideration, I think this is what the macro should look
like:
--8<---------------cut here---------------start------------->8---
(defmacro org-export-with-current-buffer-copy (&rest body)
"Apply BODY in a copy of the current buffer.
The copy preserves local variables and visibility of the original
buffer.
Point is at buffer's beginning when BODY is applied."
`(org-with-gensyms (original-buffer offset buffer-string overlays)
(let ((original-buffer (current-buffer))
(offset (1- (point-min)))
(buffer-string (buffer-string))
(overlays (mapcar
'copy-overlay (overlays-in (point-min) (point-max)))))
(with-temp-buffer
(let ((buffer-invisibility-spec nil))
(org-clone-local-variables
original-buffer
"^\\(org-\\|orgtbl-\\|major-mode$\\|outline-\\(regexp\\|level\\)$\\)")
(insert buffer-string)
(mapc (lambda (ov)
(move-overlay
ov
(- (overlay-start ov) offset)
(- (overlay-end ov) offset)
(current-buffer)))
overlays)
(goto-char (point-min))
(progn ,@body))))))
(def-edebug-spec org-export-with-current-buffer-copy (body))
--8<---------------cut here---------------end--------------->8---
In other words I think you'll want to quote the whole expansion
including the let-forms into the place of the macro call. The expansion
actually is into (org-with-gensyms... which then gets expanded further
into what you want to compile, but at that point the formal parameter of
the original macro call is already resolved. This is what happens
during (non-compiled) interpretation anyway. With that change the file
compiles and seems to work the same compiled and uncompiled.
The org-export-define-derived-backend macro seems similarly starstruck,
but I really don't know what you think the expansion should be.
Fortunately it's only used in org-e-beamer so far...
One of your recent changes introduced four test fail when org-element is
compiled. I haven't yet looked why that would be, the four tests are:
FAILED test-org-export/table-cell-alignment
FAILED test-org-export/table-cell-borders
FAILED test-org-export/table-row-ends-header-p
FAILED test-org-export/table-row-starts-header-p
The new org-e-beamer.el doesn't compile at all:
org-e-beamer.el:258:1:Error: Wrong type argument: listp, org-e-beamer-export-block
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2012-07-01 16:33 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-02 10:46 Bug: Images in Latex [7.8.11 (release_7.8.11-33-g2d71a5 @ /Users/petr/Dropbox/emacs/elisp/org-mode/lisp/)] Petr Samarin
2012-06-02 13:23 ` Jambunathan K
2012-06-02 17:16 ` new exporter (was: Bug: Images in Latex..) Achim Gratz
2012-06-03 13:21 ` new exporter Jambunathan K
2012-06-04 20:23 ` Achim Gratz
2012-06-07 19:44 ` Nicolas Goaziou
2012-06-07 19:59 ` Achim Gratz
2012-06-07 20:24 ` Nicolas Goaziou
2012-06-09 18:48 ` Achim Gratz
2012-06-09 18:56 ` Nicolas Goaziou
2012-06-09 19:06 ` Achim Gratz
2012-06-09 19:45 ` Nicolas Goaziou
2012-06-09 21:19 ` Achim Gratz
2012-06-07 20:14 ` Achim Gratz
2012-06-26 5:39 ` Achim Gratz
2012-06-26 6:18 ` Achim Gratz
2012-06-26 14:53 ` Nicolas Goaziou
2012-06-26 16:14 ` Achim Gratz
2012-06-26 18:43 ` Achim Gratz
2012-06-27 20:05 ` Achim Gratz
2012-06-28 7:03 ` Nicolas Goaziou
2012-06-29 18:17 ` Achim Gratz
2012-06-30 6:48 ` Nicolas Goaziou
2012-06-30 7:12 ` Achim Gratz
2012-07-01 16:33 ` Achim Gratz [this message]
2012-07-02 10:19 ` Nicolas Goaziou
2012-07-02 19:06 ` Achim Gratz
2012-07-12 18:37 ` Achim Gratz
2012-07-13 14:46 ` Nicolas Goaziou
2012-07-13 18:32 ` Achim Gratz
2012-07-14 16:20 ` Nicolas Goaziou
2012-07-14 16:31 ` Achim Gratz
2012-07-14 16:48 ` Jambunathan K
2012-07-14 17:47 ` Jambunathan K
2012-07-15 12:02 ` Achim Gratz
2012-07-15 19:50 ` Nicolas Goaziou
2012-07-15 20:08 ` Bastien
2012-07-15 20:18 ` Achim Gratz
2012-07-16 8:46 ` Nicolas Goaziou
2012-07-16 18:11 ` Achim Gratz
2012-07-16 21:11 ` Nicolas Goaziou
2012-07-17 17:35 ` Achim Gratz
2012-07-17 20:59 ` Nicolas Goaziou
2012-07-18 9:38 ` Nicolas Goaziou
2012-07-18 18:57 ` Achim Gratz
2012-07-18 18:09 ` Achim Gratz
2012-07-16 18:35 ` local.mk vs. default.mk (was: new exporter) Achim Gratz
-- strict thread matches above, loose matches on Subject: below --
2012-09-30 11:41 new exporter itmejl
2012-09-30 12:36 ` Nicolas Goaziou
2012-10-11 12:34 New exporter Sebastien Vauban
2012-10-11 14:07 ` Yagnesh Raghava Yakkala
2012-10-12 7:33 ` Sebastien Vauban
2012-10-11 19:37 ` Nicolas Goaziou
2012-10-12 7:34 ` Sebastien Vauban
2012-10-12 11:09 ` Sebastien Vauban
2012-10-12 11:27 ` Sebastien Vauban
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=87r4sv5tmm.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).