Re: [O] Carriage return in macro
Hello,
Timothy Aldrich wiskey5al...@gmail.com writes:
I have a simple macro defined to simplify the inclusion of a style for
odt-export. It looks like this:
#+MACRO: HEADING #+ODT:text:p style-name=MyHeading$1/text:p
and then to add this style to any text within the document, I simply call it
like this:
{{{HEADING( A really great headline )}}}
This is all fine... Until I want to apply the same process to a multi-line
section. I end up with several macro calls , one per line.
{{{BODY(line one of body)}}} {{{BODY(line two of body)}}} {{{BODY(line three
of body)}}} {{{BODY(line four of body)}}}
Is there any way to have carriage returns within the text of the
macro ?
No, there isn't. Macros target small substitutions.
I have already tried using the #+BEGIN_ODT...#+END_ODT construct, but that
*really* messes with the format of the text within it.
What do you mean? I don't know odt exporter very well, but contents of
the block should be included as-is.
Regards,
--
Nicolas Goaziou
Re: [O] [Babel] org-babel-execute-buffer gives different results than org-babel-exp-non-block-elements
Hello, Eric Schulte schulte.e...@gmail.com writes: If I understand correctly, I think :export both :results none should have the desired effect of executing the code block, not inserting the results, and keeping the code block itself in place. AFAICT, :export both :results none combination doesn't seem to produce the desired outcome with the example file. Note that the feature is only needed for elisp, since it is the only language able to modify the buffer containing the source code. If you want to run emacs lisp at export time but don't want the code or the results, maybe it would be a more natural fit for a filter function? I think the OP wants (org-babel-execute-buffer) and (org-export-execute-babel-code) to behave the same in this specific situation. So, it's not export-specific. To put it differently, he wants to disable code replacement with value (which is specific to the export part of Babel). Regards, -- Nicolas Goaziou
Re: [O] Ignored in-buffer settings and after-export hook
Hello, Daniel Gerber daniel.g.ger...@gmail.com writes: 2. Is the after-export hook gone with the new exporter framework? I used this to get the list of a project's exported files: (setq html-files-list () org-publish-after-export-hook (lambda () (add-to-list 'html-files-list (buffer-file-name (current-buffer) (org-publish the-org-project t) (print html-files-list) but in 8.0.7 maint the hook is ignored altogether. `org-publish-before-export-hook' and `org-publish-after-export-hook' are not present in Org 8+, indeed. Can't you simply use `org-export-before-parsing-hook' instead? Regards, -- Nicolas Goaziou
Re: [O] Ignored in-buffer settings and after-export hook
Hi, On 26/08/2013 13:45, Nicolas Goaziou wrote: Hello, Daniel Gerber daniel.g.ger...@gmail.com writes: 2. Is the after-export hook gone with the new exporter framework? I used this to get the list of a project's exported files: (setq html-files-list () org-publish-after-export-hook (lambda () (add-to-list 'html-files-list (buffer-file-name (current-buffer) (org-publish the-org-project t) (print html-files-list) but in 8.0.7 maint the hook is ignored altogether. `org-publish-before-export-hook' and `org-publish-after-export-hook' are not present in Org 8+, indeed. Can't you simply use `org-export-before-parsing-hook' instead? I guess I can, but it means re-doing the mapping sources to exported file names. By the way, the manual points to http://orgmode.org/worg/org-configs/org-hooks.html which still lists the older hooks. Thanks for your answer!
[O] don't show author and date on odt export?
Hi, I'm trying to figure out how best to tell org not to display my name and the date at the top of the page when it exports document. Currently, it seems I can do htis by setting #+OPTIONS: author:nil date:nil However, this also removes the relevant info from the file metadata. I would prefer to somehow change the export template so that these lines aren't produced. Anyone know if that's possible? Would I have to modify ox-odt.el directly -- and is that hard to do? It looks like the relevant lines in that file are around 1488-1541. I'm a little loathe to modify the code directly though, as I like to just git pull from the master branch... Thanks! Matt
Re: [O] don't show author and date on odt export?
On Mon, Aug 26, 2013 at 2:49 PM, Matt Price mopto...@gmail.com wrote: I'm trying to figure out how best to tell org not to display my name and the date at the top of the page when it exports document. Currently, it seems I can do htis by setting #+OPTIONS: author:nil date:nil However, this also removes the relevant info from the file metadata. I would prefer to somehow change the export template so that these lines aren't produced. Anyone know if that's possible? Would I have to modify ox-odt.el directly -- and is that hard to do? It looks like the relevant lines in that file are around 1488-1541. I'm a little loathe to modify the code directly though, as I like to just git pull from the master branch... I realize I also don't quite understand how to preformat the header and footer of each page. I feel like this should be possible, as at least some footer info is generated by default (page number in centre of footer). But despite some inspection of both ox-odt.el and the styles.xml and content.xml of my exported document, I can't figure out how the content of the footer is determined. Thanks again! Matt
Re: [O] [PATH] [NEW EXPORTER] two slide backends for contrib
I just came across this, having missed it in February. Rick, I was wondering if you had thought about enabling some of deck.js's snazzier features -- transitions for text elements, for instance, like we see in the intro deck here: http://imakewebthings.com/deck.js/#intro I'm mostly asking because I'd like to try and copy your work to make an exporter for impress.js (https://github.com/bartaz/impress.js). Kinjo has written one, but it uses the old exporter and no longer works with current versions of org, so I thought I would start with your deck.js work. I know that's not very specific, but if you've thought about these issues I would love to learn wat you've figured out. Thanks! Matt On Wed, Feb 20, 2013 at 10:34 AM, Bastien b...@altern.org wrote: Hi Rick, Rick Frankel r...@rickster.com writes: Attached are: - ox-deck.el - ox-s5.el Which, respectively, provide deck.js and s5 backends for the new exporter. I would be happy for these to be included in contrib. Note that I have already signed the FSF assignment documents, so they can be safely included in the core if so desired. Added to contrib/, thanks a lot! I modified the Copyright line to tell that the copyright is your own, you don't need to assign copyright to the FSF for code in contrib/. If you have time, please mention those packages in Worg: http://orgmode.org/worg/org-contrib/ (Just send me your public key to get push access to Worg.) All best, -- Bastien
