Re: [O] New exporter and dates in tables

OK, thank you. - Carsten On 9.8.2013, at 13:02, Bernt Hansen wrote: > Hi Carsten! > > All of my headings are followed by an inactive timestamp. I've started > leaving a blank line before the content for the heading so the inactive > timestamp is not exported when timestamps are disabled with

Re: [O] New exporter and dates in tables

Hi Carsten! All of my headings are followed by an inactive timestamp. I've started leaving a blank line before the content for the heading so the inactive timestamp is not exported when timestamps are disabled with the <:nil option. This works fine for me. Regards, Bernt Carsten Dominik write

Re: [O] New exporter and dates in tables

Hi guys, did you arrive at a conclusion of this thread, or is this still open? Thanks - Carsten On 16.4.2013, at 09:48, Bastien wrote: > Hi Nicolas, > > Nicolas Goaziou writes: > >> Bastien writes: >> >>> Nicolas Goaziou writes: >>> We can widen the definition of `standalone': a s

Re: [O] [New Exporter] org-export-latex-after-initial-vars-hook

> Is there a hook that is run before actual LaTeX export of a given > org-mode buffer in the new exporter engine? > For reference: I got it to work by adapting the snippet from Bruno Tavernier[1]: #+begin_src emacs-lisp (defun my-auto-tex-cmd (backend) "When exporting from .org with latex,

Re: [O] [New Exporter] org-export-latex-after-initial-vars-hook

To minimize risk of eye cancer (previous version was sent from gmail web interface at work without plain text setting) here it goes again: Nicolas Goaziou writes: > Søren Mikkelsen writes: >> But I have a problem with the exporter: >> >> I have modified by org-exporter to export latex-files wi

Re: [O] [New Exporter] org-export-latex-after-initial-vars-hook

Nicolas Goaziou writes: > Søren Mikkelsen writes: >>* But I have a problem with the exporter:* >>** >*> I have modified by org-exporter to export latex-files with the xelatex* >*> compiler. The implementation uses the* >*> "org-export-latex-after-initial-vars-hook"-hook to reconfigure the* >>*

Re: [O] {New exporter] What happened to the export template

Hi Robert, Robert Goldman writes: > A very late follow-up: > > I note that the Worg instructions for HTML export still cite > org-insert-export-options-template: > > http://orgmode.org/worg/org-tutorials/org-publish-html-tutorial.html Can you fix this? Please send me your public key if you d

Re: [O] {New exporter] What happened to the export template

A very late follow-up: I note that the Worg instructions for HTML export still cite org-insert-export-options-template: http://orgmode.org/worg/org-tutorials/org-publish-html-tutorial.html

Re: [O] [new exporter] how can I export drawers?

Carsten Dominik writes: > You did not, I wanted to tell you that your input is appreciated. Thanks! -- : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D : in Emacs 24.3.50.1 and Org release_8.0.2-67-gc36435

Re: [O] [new exporter] how can I export drawers?

On 2.5.2013, at 21:28, Eric S Fraga wrote: > Carsten Dominik writes: > > [...] > >> Hi Eric, >> >> I can see that this must be painful, so you are one of the >> people who suffer from this more that others. On the other >> hand, this also makes you an asset for Org-mode, because >> you keep

Re: [O] [new exporter] how can I export drawers?

Carsten Dominik writes: [...] > Hi Eric, > > I can see that this must be painful, so you are one of the > people who suffer from this more that others. On the other > hand, this also makes you an asset for Org-mode, because > you keep testing the exporter in many different ways. > > I hope that

Re: [O] [new exporter] how can I export drawers?

On 1.5.2013, at 14:28, Eric S Fraga wrote: > "Thomas S. Dye" writes: > >> Hi Eric, >> >> I haven't been following closely, so I'm just checking that you're aware >> of a new variable org-export-allow-bind-keywords, which could play a >> role in the behavior you are seeing. > > Thanks Tom. I

Re: [O] [new exporter] how can I export drawers?

"Thomas S. Dye" writes: > Hi Eric, > > I haven't been following closely, so I'm just checking that you're aware > of a new variable org-export-allow-bind-keywords, which could play a > role in the behavior you are seeing. Thanks Tom. I am indeed aware of this variable. And it usually works. F

Re: [O] [new exporter] how can I export drawers?

Hi Eric, I haven't been following closely, so I'm just checking that you're aware of a new variable org-export-allow-bind-keywords, which could play a role in the behavior you are seeing. hth, Tom Eric S Fraga writes: > Nicolas, > > further on this: I got my original document working. I had a

Re: [O] [new exporter] how can I export drawers?

Nicolas, further on this: I got my original document working. I had a d:nil line hidden away in the document which took precedence over my other attempts to ask for drawers to be exported. Sorry about bothering everybody with this. However, I am still having some strange random behaviour to do

Re: [O] [new exporter] how can I export drawers?

Nicolas Goaziou writes: [...] > I don't understand your problem. Drawers are correctly exported here. > Could you provided an ECM? Arggghhh. An ECM I just created works just fine. There's obviously something obscurely wrong in my long document that prevents drawers from being exported. I wil

Re: [O] [new exporter] how can I export drawers?

Nicolas Goaziou writes: > Thorsten Jolitz writes: > >> I would like to be able to export drawers to ASCII too, although, as >> Nicolas mentioned in an earlier thread, the ascii exporter currently >> does not handle this. > > Did I say that? > > AFAICT, drawers are correctly exported in ASCII exp

Re: [O] [new exporter] how can I export drawers?

Hello, Thorsten Jolitz writes: > I would like to be able to export drawers to ASCII too, although, as > Nicolas mentioned in an earlier thread, the ascii exporter currently > does not handle this. Did I say that? AFAICT, drawers are correctly exported in ASCII export. Regards, -- Nicolas G

Re: [O] [new exporter] how can I export drawers?

Hello, Eric S Fraga writes: > I am going a little crazy here! I have an org document which I need to > export to PDF using latex. Everything works just fine with the new > exporter except for one thing: I cannot get it to export drawers. I > have set org-export-with-drawers to t, I have set "

Re: [O] [new exporter] how can I export drawers?

Eric S Fraga writes: > I am going a little crazy here! I have an org document which I need to > export to PDF using latex. [not an answer, but rather a feature request] I would like to be able to export drawers to ASCII too, although, as Nicolas mentioned in an earlier thread, the ascii expor

[O] [new exporter] how can I export drawers?

Hello, I am going a little crazy here! I have an org document which I need to export to PDF using latex. Everything works just fine with the new exporter except for one thing: I cannot get it to export drawers. I have set org-export-with-drawers to t, I have set "d:t" in the OPTIONS line, I hav

Re: [O] [New Exporter] org-export-latex-after-initial-vars-hook

Hello, Søren Mikkelsen writes: > But I have a problem with the exporter: > > I have modified by org-exporter to export latex-files with the xelatex > compiler. The implementation uses the > "org-export-latex-after-initial-vars-hook"-hook to reconfigure the > default process, however, this hook s

[O] [New Exporter] org-export-latex-after-initial-vars-hook

Hello, I have just upgraded to the Org 8.0. Nice work! :) But I have a problem with the exporter: I have modified by org-exporter to export latex-files with the xelatex compiler. The implementation uses the "org-export-latex-after-initial-vars-hook"-hook to reconfigure the default process, h

Re: [O] New exporter - publishing org files doesn't include :tangle

Bernt Hansen writes: > Nicolas Goaziou writes: > >> Hello, >> >> Bernt Hansen writes: >> >>> So far my attempts using this workaround have failed and I can't get >>> :tangle in my exported org file. I think I also would prefer to have >>> the :exports value in the .org source as well so it's a

Re: [O] New exporter - publishing org files doesn't include :tangle

Nicolas Goaziou writes: > Hello, > > Bernt Hansen writes: > >> So far my attempts using this workaround have failed and I can't get >> :tangle in my exported org file. I think I also would prefer to have >> the :exports value in the .org source as well so it's a true >> representation of the so

Re: [O] New exporter - publishing org files doesn't include :tangle

Hello, Bernt Hansen writes: > So far my attempts using this workaround have failed and I can't get > :tangle in my exported org file. I think I also would prefer to have > the :exports value in the .org source as well so it's a true > representation of the source. There was a bug in org back-e

Re: [O] New exporter - publishing org files doesn't include :tangle

Nicolas Goaziou writes: > Hello, > > Bernt Hansen writes: > >> James Yuan noticed that the .org file that is published with my document >> (http://doc.norang.ca/org-mode.org does not contain :tangle on any of >> the source blocks. >> >> One of the uses of this document is to pull up the file and

Re: [O] New exporter - publishing org files doesn't include :tangle

Nicolas Goaziou writes: > Hello, > > Bernt Hansen writes: > >> James Yuan noticed that the .org file that is published with my document >> (http://doc.norang.ca/org-mode.org does not contain :tangle on any of >> the source blocks. >> >> One of the uses of this document is to pull up the file and

Re: [O] New exporter - publishing org files doesn't include :tangle

Nicolas Goaziou writes: > Hello, > > Bernt Hansen writes: > >> James Yuan noticed that the .org file that is published with my document >> (http://doc.norang.ca/org-mode.org does not contain :tangle on any of >> the source blocks. >> >> One of the uses of this document is to pull up the file and

Re: [O] New exporter - publishing org files doesn't include :tangle

Hello, Bernt Hansen writes: > James Yuan noticed that the .org file that is published with my document > (http://doc.norang.ca/org-mode.org does not contain :tangle on any of > the source blocks. > > One of the uses of this document is to pull up the file and tangle it to > create an emacs confi

[O] New exporter - publishing org files doesn't include :tangle

Hi Nicolas, James Yuan noticed that the .org file that is published with my document (http://doc.norang.ca/org-mode.org does not contain :tangle on any of the source blocks. One of the uses of this document is to pull up the file and tangle it to create an emacs configuration but this seems to be

Re: [O] New Exporter: plain list depth

Hi, At Mon, 22 Apr 2013 00:10:25 +0200, Nicolas Goaziou wrote: > > Yasushi SHOJI writes: > > > To generate "--" at the list 2.1, I'd like to find out the list 2.1 is > > at depth 2, so that I can use (make-string 2 ?-) for my bullet. > > Something like the following should work, assuming ITEM

Re: [O] New Exporter: plain list depth

Hello, Yasushi SHOJI writes: > What is the best way to know the depth of list entries when I writing > an exporter back-end? > > let's say I have: > > #+BEGIN_SRC org > * headline 1 > - list 1 > - list 2 > - list 2.1 > #+END_SRC > > I'd like to convert it to: > > #+BEGIN_EXAMPLE

[O] New Exporter: plain list depth

Hi, What is the best way to know the depth of list entries when I writing an exporter back-end? let's say I have: #+BEGIN_SRC org * headline 1 - list 1 - list 2 - list 2.1 #+END_SRC I'd like to convert it to: #+BEGIN_EXAMPLE * headline 1 - list 1 - list 2 -- list 2.1 #+

Re: [O] New exporter and defgroup

Bastien writes: >> Can we have some sort of a check while loading Org that picks up these >> shadowed variables and "deletes" them? > > I think Achim has been thinking about some incantation for this > (at install time). Maybe if this can be done after installation, > we could document it somewher

Re: [O] New exporter and defgroup

Hi, yes, this *is* a problem. Suvayu Ali writes: > Can we have some sort of a check while loading Org that picks up these > shadowed variables and "deletes" them? I think Achim has been thinking about some incantation for this (at install time). Maybe if this can be done after installation, w

Re: [O] New exporter and defgroup

Hi Christian, On Fri, Apr 19, 2013 at 02:52:46PM +0200, Christian Egli wrote: > Hi all > > The new exporter engine has changed the defcustom names but seems to > have kept the names of the defgroups (at least in the case of > taskjuggler). This is good as it allowed me to make some > backward-inc

[O] New exporter and defgroup

Hi all The new exporter engine has changed the defcustom names but seems to have kept the names of the defgroups (at least in the case of taskjuggler). This is good as it allowed me to make some backward-incompatible changes. On the other hand when I do a M-x customize-group RET org-export-taskjug

Re: [O] New exporter and dates in tables

Hi Nicolas, Nicolas Goaziou writes: > Bastien writes: > >> Nicolas Goaziou writes: >> >>> We can widen the definition of `standalone': a standalone timestamp is >>> a timestamp belonging to a paragraph that contains only timestamps >>> objects. >> >> Great. If that's possible, then I think th

Re: [O] New exporter and dates in tables

Nicolas Goaziou writes: > The following patch should do that. It comes with tests, but it should > be tested extensively, if only to know if this feature is as useful as > it seems. Thanks a lot. I will not be online for the next 5 hours, but I'll think about this. -- Bastien

Re: [O] New exporter and dates in tables

Nicolas You may want to extract the below function as a useful API. You can then plug that in into `org-odt--standalone-link-p' and it's counterpart in ox-html.el. I am not closely tracking changes in ox-html.el, so things might have moved since. Jambunathan K. Nicolas Goaziou writes: > +

Re: [O] New exporter and dates in tables

Bastien writes: > Nicolas Goaziou writes: > >> We can widen the definition of `standalone': a standalone timestamp is >> a timestamp belonging to a paragraph that contains only timestamps >> objects. > > Great. If that's possible, then I think that's the best solution. The following patch shou

Re: [O] New exporter and dates in tables

Nicolas Goaziou writes: > We can widen the definition of `standalone': a standalone timestamp is > a timestamp belonging to a paragraph that contains only timestamps > objects. Great. If that's possible, then I think that's the best solution. -- Bastien

Re: [O] New exporter and dates in tables

Bastien writes: > Nicolas Goaziou writes: > >> Then why do you suggest to drop the idea (for now)? > > Because IIUC, the time-stamps would not be ignored here > > * Task > <2013-04-14 dim.> > <2013-04-16 dim.> > > because > > <2013-04-14 dim.> > <2013-04-16 dim.> > > is a paragraph. (Th

Re: [O] New exporter and dates in tables

Nicolas Goaziou writes: > Then why do you suggest to drop the idea (for now)? Because IIUC, the time-stamps would not be ignored here * Task <2013-04-14 dim.> <2013-04-16 dim.> because <2013-04-14 dim.> <2013-04-16 dim.> is a paragraph. (The agenda takes both time-stamps into accoun

Re: [O] New exporter and dates in tables

Bastien writes: > Nicolas Goaziou writes: > >> According to your suggestion, with `org-export-with-timestamps' set to >> `not-standalone', in the following example: >> >> * Task >> >> >> At , I must do that. >> >> the first would be ignored, not the second one. Isn't it >> what you want? > >

Re: [O] New exporter and dates in tables

Hi Nicolas, Nicolas Goaziou writes: > According to your suggestion, with `org-export-with-timestamps' set to > `not-standalone', in the following example: > > * Task > > > At , I must do that. > > the first would be ignored, not the second one. Isn't it > what you want? Yes, exactly. --

Re: [O] New exporter and dates in tables

Hello, Bastien writes: > Let's not implement my proposal and stick to your implementation of > the exceptions you first proposed. Before we throw the baby out with the bath water, I want to make sure we are understanding each other. > I expect users will want a way to get rid of in > > * Task

Re: [O] New exporter and dates in tables

"Sebastien Vauban" writes: > Wouldn't it be a good moment to introduce > > APPT: <2013-04-13 Sat> > > or maybe better named > > EVENT: <2013-04-13 Sat> > > for things that only apply for today? In master, there is the new agenda entry type :scheduled* and the new agenda type agenda*. So y

Re: [O] New exporter and dates in tables

Hi Nicolas, Nicolas Goaziou writes: > Bastien writes: > >> I would find it both cleaner and more useful for users to extend >> `org-export-with-timestamps' with three choices: >> >> 'inactive-not-standalone >> 'active-not-standalone >>'not-standalone > > This is a different id

Re: [O] New exporter and dates in tables

Hello, Nicolas Goaziou wrote: > Bastien writes: > >> I would find it both cleaner and more useful for users to extend >> `org-export-with-timestamps' with three choices: >> >> 'inactive-not-standalone >> 'active-not-standalone >>'not-standalone > > This is a different idea. The

Re: [O] New exporter and dates in tables

Bastien writes: > I would find it both cleaner and more useful for users to extend > `org-export-with-timestamps' with three choices: > > 'inactive-not-standalone > 'active-not-standalone >'not-standalone This is a different idea. The change would happen at the exporter level,

Re: [O] New exporter and dates in tables

Nicolas Goaziou writes: > Is that OK with you? I still resist this idea. I would find it both cleaner and more useful for users to extend `org-export-with-timestamps' with three choices: 'inactive-not-standalone 'active-not-standalone 'not-standalone When set to 'not-standalo

Re: [O] New exporter and dates in tables

Hello, Bastien writes: > Nicolas Goaziou writes: > >> Thinking more about it, I think I need to make some more exceptions >> anyway. For example timestamps in clock lines and in planning info >> shouldn't react to `org-export-with-timestamps' (it would be silly to >> have `org-export-with-plann

Re: [O] New exporter and dates in tables

Hello, Nicolas Goaziou writes: > Thinking more about it, I think I need to make some more exceptions > anyway. For example timestamps in clock lines and in planning info > shouldn't react to `org-export-with-timestamps' (it would be silly to > have `org-export-with-planning' set to t and still s

Re: [O] New exporter and dates in tables

Hello, Bastien writes: > Note that Org 8.0-pre comes with a new export option > `org-export-with-planning' which handles the export of > SCHEDULED / DEADLINE / CLOSED time-stamps. > > This used to be the job of org-export-with-timestamps. > > I guess many people who used (setq org-export-with-ti

Re: [O] New exporter and dates in tables

Hi all, Note that Org 8.0-pre comes with a new export option `org-export-with-planning' which handles the export of SCHEDULED / DEADLINE / CLOSED time-stamps. This used to be the job of org-export-with-timestamps. I guess many people who used (setq org-export-with-timestamps nil) now want (setq

Re: [O] New exporter and dates in tables

This looks good to me - with my limited understanding of the exporter lingo. Thanks! - Carsten On 10 apr. 2013, at 14:43, Nicolas Goaziou wrote: > Hello, > > Carsten Dominik writes: > >> Some people throw in time stamps often while they work, just >> as a little label, indicating that they

Re: [O] New exporter and dates in tables

Hello, Carsten Dominik writes: > Some people throw in time stamps often while they work, just > as a little label, indicating that they were working on this > at a specific date, or that the entry was created on a specific > date. Many people I know have a hook that throws in such a > time stam

Re: [O] new exporter and plain text table export alignment

maxco...@gmail.com writes: > Nicolas Goaziou writes: >> >> Thank you for the detailed report. Unfortunately (or fortunately), >> I cannot reproduce it with Org-mode version 8.0-pre >> (release_8.0-pre-333-g728c69). >> >> What version do you use? >> >> >> Regards, > > the same, (release_8.0-pre-3

Re: [O] new exporter and plain text table export alignment

Nicolas Goaziou writes: > > Thank you for the detailed report. Unfortunately (or fortunately), > I cannot reproduce it with Org-mode version 8.0-pre > (release_8.0-pre-333-g728c69). > > What version do you use? > > > Regards, the same, (release_8.0-pre-333-g728c69) I was afraid of that. Thanks

Re: [O] new exporter and plain text table export alignment

Hello, maxco...@gmail.com writes: > I use org tables to estimate construction projects. I frequently use > simple math within a table cell to help me remember what I was > thinking when I entered the data. > > It seems that the new exporter does not align plain text exports in > some of these si

Re: [O] New exporter and dates in tables

On 8 apr. 2013, at 21:49, Nicolas Goaziou wrote: > Hello, > > Carsten Dominik writes: > >> On 8 apr. 2013, at 13:27, Bernt Hansen wrote: >> >>> Nicolas Goaziou writes: >>> Bernt Hansen writes: > I have subtrees with inactive timestamps in the text indicating when > som

[O] new exporter and plain text table export alignment

Hi all I use org tables to estimate construction projects. I frequently use simple math within a table cell to help me remember what I was thinking when I entered the data. It seems that the new exporter does not align plain text exports in some of these situations. I only use plain text and ht

Re: [O] New exporter and latex table export with floats in engineering notation

Hi Dieter, "Dieter Wilhelm, H." writes: > with 8.0pre I'm currently getting strange results when exporting to > latex a table with the following notations > > | -7.8E-2 | \(-7.8e-2\)| Please let us know what is the result, otherwise we cannot see what is "strange". Thanks! PS: http://orgmode.

[O] New exporter and latex table export with floats in engineering notation

Hi (), with 8.0pre I'm currently getting strange results when exporting to latex a table with the following notations | -7.8E-2 | \(-7.8e-2\)| what shall I do? The only thing I manage in this situation is | -7.8 10^-2 | but this is unhandy especially when importing floats... -- Best wishes

Re: [O] New exporter problem with #+AUTHOR

Hello, Bernt Hansen writes: > I have the following line in my org-mode document > > #+AUTHOR: Bernt Hansen (IRC:BerntH on freenode) > > On the old exporter this became > > > > I just tried exporting this with the new exporter and I get this > > BerntH > on freenode)"/> > > which isn't legal HTM

Re: [O] New exporter and dates in tables

Hello, Carsten Dominik writes: > On 8 apr. 2013, at 13:27, Bernt Hansen wrote: > >> Nicolas Goaziou writes: >> >>> Bernt Hansen writes: >>> I have subtrees with inactive timestamps in the text indicating when something occurred. I normally don't want to export these. But I think

Re: [O] New exporter problem with #+AUTHOR

Hi Bernt, Nicolas Goaziou writes: > Well, technically, irc:BerntH is a plain link, like http://orgmode.org, > since irc: is a valid protocol. That may bite you in other parts of the > document. As a workaround, you can also remove org-irc.el from `org-modules' so that irc:... is not recognized

Re: [O] New exporter and dates in tables

On 8 apr. 2013, at 13:27, Bernt Hansen wrote: > Nicolas Goaziou writes: > >> Bernt Hansen writes: >> >>> I have subtrees with inactive timestamps in the text indicating when >>> something occurred. I normally don't want to export these. But I think >>> any table data that includes inactive

Re: [O] New exporter and dates in tables

Nicolas Goaziou writes: > Bernt Hansen writes: > >> I have subtrees with inactive timestamps in the text indicating when >> something occurred. I normally don't want to export these. But I think >> any table data that includes inactive timestamps should be an exception >> to this ... otherwise

Re: [O] New exporter problem with #+AUTHOR

Hello, Bernt Hansen writes: > I have the following line in my org-mode document > > #+AUTHOR: Bernt Hansen (IRC:BerntH on freenode) > > On the old exporter this became > > > > I just tried exporting this with the new exporter and I get this > > BerntH > on freenode)"/> > > which isn't legal HTM

Re: [O] New exporter and dates in tables

Hello, Bernt Hansen writes: > I have subtrees with inactive timestamps in the text indicating when > something occurred. I normally don't want to export these. But I think > any table data that includes inactive timestamps should be an exception > to this ... otherwise you get output tables wi

Re: [O] New exporter and dates in tables

On Apr 7, 2013, at 8:05 PM, Bernt Hansen wrote: > Hi Nicolas, > > I just noticed that the new exporter does not export inactive timestamps > in table columns. This is now controlled by the option <:t > > I think this is a change from the old exporter (but I'm not sure it's > really wrong). T

[O] New exporter and dates in tables

Hi Nicolas, I just noticed that the new exporter does not export inactive timestamps in table columns. This is now controlled by the option <:t I think this is a change from the old exporter (but I'm not sure it's really wrong). I have subtrees with inactive timestamps in the text indicating wh

Re: [O] New exporter and publishing to HTML with styles

Nicolas Goaziou writes: > Hello, > > Bernt Hansen writes: > >> I'm playing with the new exporter and publishing. Everything seems to >> be good > > Nice. > >> except my style sheet details are missing. > > Not nice. ;) > >> There are :style entries in my org-publish-project-alist which seem to

Re: [O] New exporter and publishing to HTML with styles

Hello, Bernt Hansen writes: > I'm playing with the new exporter and publishing. Everything seems to > be good Nice. > except my style sheet details are missing. Not nice. ;) > There are :style entries in my org-publish-project-alist which seem to > be ignored -- there are no style details i

[O] New exporter and publishing to HTML with styles

Hi Nicolas, I'm playing with the new exporter and publishing. Everything seems to be good except my style sheet details are missing. There are :style entries in my org-publish-project-alist which seem to be ignored -- there are no style details in the published HTML file (see http://norang.ca/tm

[O] New exporter problem with #+AUTHOR

Hi Nicolas, I have the following line in my org-mode document #+AUTHOR: Bernt Hansen (IRC:BerntH on freenode) On the old exporter this became I just tried exporting this with the new exporter and I get this BerntH on freenode)"/> which isn't legal HTML. The quotes on the href="BerntH" clos

Re: [O] New Exporter BUG/Change in behaviour

Nicolas Goaziou writes: > Thorsten Jolitz writes: > >> Nicolas Goaziou writes: >> >>> No. The "d:" item only applies to regular drawers. >>> >>> `property-drawer' elements are not among them. Back-ends handle these >>> beasts as they see fit (they usually ignore them, as you can tell). >> >> I

Re: [O] New Exporter BUG/Change in behaviour

Thorsten Jolitz writes: > Nicolas Goaziou writes: > >> No. The "d:" item only applies to regular drawers. >> >> `property-drawer' elements are not among them. Back-ends handle these >> beasts as they see fit (they usually ignore them, as you can tell). > > I actually have a use-case where I woul

Re: [O] New Exporter BUG/Change in behaviour

Nicolas Goaziou writes: > No. The "d:" item only applies to regular drawers. > > `property-drawer' elements are not among them. Back-ends handle these > beasts as they see fit (they usually ignore them, as you can tell). I actually have a use-case where I would like to export the property-drawer

Re: [O] New Exporter BUG/Change in behaviour

Hello, Thorsten Jolitz writes: > Shouldn't the > > ,- > | :EXPORT_OPTIONS: d:t > `- > > setting in the following minimal org-file export the property-drawer for > this subtree too? > > ,--- > | * header1 > | :PROPERTIES: > | :EXPORT

Re: [O] New Exporter BUG/Change in behaviour

Nicolas Goaziou writes: Hello, > The new exporter distinguishes between subtree export (toggled with C-s > key within the dispatcher) and region export. In the old exporter, C-c @ > + export command would give you a subtree export. This is not the case > in the new exporter. You have to explicit

Re: [O] New Exporter BUG/Change in behaviour

Nicolas Goaziou writes: > Hello, > > Bernt Hansen writes: > >> Is this a bug? > > No, it isn't. > >> My current workaround is to delete the global #+OPTIONS >> line (but that doesn't feel right since I have to add it back to export >> what is left to do for the entire file when sharing it with o

Re: [O] New Exporter BUG/Change in behaviour

Hello, Bernt Hansen writes: > My org file has > > #+OPTIONS: tasks:todo > > This globally skips DONE tasks in my exports when I export the entire > file in both the old and new exporter. > > If I select a task with C-c @ that is DONE (or any done state) and try > to export that in the new export

[O] New Exporter BUG/Change in behaviour

Hi Nicolas, I finally updated to the latest master branch at work yesterday to move to the new exporter and found the following change I don't know how to deal with. My org file has #+OPTIONS: tasks:todo This globally skips DONE tasks in my exports when I export the entire file in both the old

Re: [O] New Exporter html - latex - beamer

Charles Berry writes: > ucsd.edu> writes: > >> >> Robert Eckl gmx.de> writes: >> > [snip] >> > > I said > >> You might be able to do what you want with filter functions. >> > >> >> You can do that with this filter: >> > > But you will want to add something to it to treat links without th

Re: [O] New Exporter html - latex - beamer

ucsd.edu> writes: > > Robert Eckl gmx.de> writes: > [snip] > I said > You might be able to do what you want with filter functions. > > > You can do that with this filter: > But you will want to add something to it to treat links without the :windowenv: tag in the normal way > , >

Re: [O] New Exporter html - latex - beamer

Robert Eckl writes: > Eric S Fraga writes: > >> Robert Eckl writes: >> >>> I have to provide weekly newsletters in the format pdf and html. Up to >>> now i did this with exporting to scrartcl, known as koma-script. >>> Including images is a bit booring because i handle two formats, for example

Re: [O] New Exporter html - latex - beamer

Eric S Fraga writes: > Robert Eckl writes: > >> I have to provide weekly newsletters in the format pdf and html. Up to >> now i did this with exporting to scrartcl, known as koma-script. >> Including images is a bit booring because i handle two formats, for example > > I am not sure what your la

Re: [O] [new-exporter] org-export-before-parsing-hook GOTCHA

Hi Charles, Charles Berry writes: > Is this a feature or a bug? A bug: the user is not supposed to be so careful. This should be fixed now, thanks! -- Bastien

Re: [O] [New exporter] Org LaTeX markup

Charles Berry ucsd.edu> writes: > [snip] > > > > Can you give me a hint? > > M-x customize-variable RET org-latex-format-headline-function RET > > then copy and paste the last part of the docstring into the window - add a > closing parenthesis at the end - and then modify it to your taste.

Re: [O] New Exporter html - latex - beamer

Robert Eckl writes: > I have to provide weekly newsletters in the format pdf and html. Up to > now i did this with exporting to scrartcl, known as koma-script. > Including images is a bit booring because i handle two formats, for example I am not sure what your latex bits are trying to accomplis

[O] [new-exporter] org-export-before-parsing-hook GOTCHA

Is this a feature or a bug? in org-export-as, there are these lines , | (goto-char (point-min)) | (run-hook-with-args 'org-export-before-parsing-hook backend) ` For some time, I used hook functions that usually reset the position of *point*. They worked fine. Recently, they produced s

Re: [O] New Exporter html - latex - beamer

Dnia 2013-03-15, o godz. 21:55:42 Robert Eckl napisał(a): > Both, the old and the new Exporter are brilliant tools, migration to > the new exporter didn't make great issues. > I have to provide weekly newsletters in the format pdf and html. Up to > now i did this with exporting to scrartcl, known

[O] New Exporter html - latex - beamer

Both, the old and the new Exporter are brilliant tools, migration to the new exporter didn't make great issues. I have to provide weekly newsletters in the format pdf and html. Up to now i did this with exporting to scrartcl, known as koma-script. Including images is a bit booring because i handle

Re: [O] [New Exporter] deriving from derived backends?

Hello, Rick Frankel writes: > I am trying to derive a backend from another derived backend (i want > to override certain entries in the options-alist), but it does not > seem to work. The menu entries are created, but the in the > second-level derived backend are not being picked up. > > Should

Re: [O] [new-exporter] Beamer color theme

On Fri, Mar 15, 2013 at 01:57:26PM +, Eric S Fraga wrote: > > I have updated, on Worg, the example presentation to work with the new > exporter. It is at > > http://orgmode.org/worg/exporters/beamer/presentation.org > > Can you put a link to it from the tutorial maybe? Done :).

Re: [O] [new-exporter] Beamer color theme

Suvayu Ali writes: > On Wed, Mar 13, 2013 at 07:11:09AM +0530, Vikas Rawal wrote: >> How do I change beamer color theme in the new exporter. > > I updated the tutorial. Suvayu, thanks for this. I have updated, on Worg, the example presentation to work with the new exporter. It is at http://o

  1   2   3   4   5   6   7   >