Re: [O] [NEW EXPORTER] [BUG] HTML_CONTAINER_CLASS property ignored

Hi Rick, Rick Frankel writes: > My guess is that on ox-html.el:1917 (the only reference to > :html-container-class) > >(extra-class (org-element-property :html-container-class headline)) > > should be > >(extra-class (org-element-property :HTML_CONTAINER_CLASS headline)) > > Does th

Re: [O] [new exporter][latex] does org-preview-latex-fragment use #+latex_header ?

Just adding some more information. It gets curiouser and curiouser... Myles English writes: > Hi, > > I have just pulled from git and have been migrating to use the new > exporter. > > I have a problem where org-preview-latex-fragment appears not to use a > style file the latex header. > > Sta

Re: [O] [new exporter] 2 questions

Nicolas Goaziou writes: > Note that filling/auto-filling will never put you in this situation, > since Org has a protection mechanism. IOW, if you end up with a list > marker at the beginning of a line, it's your fault. I don't use auto-fill in formulas. And yes, I take responsibility for my faul

Re: [O] [new exporter] 2 questions

Achim Gratz writes: > Nicolas Goaziou writes: >> True, that's why there's also inline \[...\]. But you have to accept >> paragraph limitations (no empty line, do not start a line with list >> markers...). > > Now, given that difference and the fact that these things can span > over multiple lines

Re: [O] [new exporter] 2 questions

Nicolas Goaziou writes: > True, that's why there's also inline \[...\]. But you have to accept > paragraph limitations (no empty line, do not start a line with list > markers...). Now, given that difference and the fact that these things can span over multiple lines and thus include the beginning

Re: [O] [new exporter] 2 questions

Achim Gratz writes: > There is one remaining difference to a display equation or LaTeX > fragment: the LaTeX environment will apparently always end the > paragraph, Indeed. A LaTeX environment has got the same syntactical value as a paragraph (both are elements): they cannot be nested. > someth

Re: [O] [new exporter] 2 questions

Nicolas Goaziou writes: > I gave you a solution since the beginning of this thread: use a latex > environment. After a bit of searching: the answer was in another thread, not in answer to my original question and I read that answer as "LaTeX blocks are equivalent to LaTeX environments". I see now

Re: [O] [new exporter] 2 questions

Achim Gratz writes: >> I gave you a solution since the beginning of this thread: use a latex >> environment. > > It is not a solution because it does not export to HTML. Of course it does. Try: --8<---cut here---start->8--- Some latex \begin{equation*} 2 + 2

Re: [O] [new exporter] 2 questions

Nicolas Goaziou writes: > I gave you a solution since the beginning of this thread: use a latex > environment. It is not a solution because it does not export to HTML. If I need to write the document mostly in LaTeX I can start with LaTeX and and then use some LaTeX to HTML translation. Regards

Re: [O] [new exporter] 2 questions

Achim Gratz writes: > Nicolas Goaziou writes: >> The parser parses Org syntax. If you see something else, unless there is >> an obvious bug, then you are expecting the Org syntax to be different >> from what it is. It's even the goal of the parser: to define the way to >> read Org syntax. > > Tha

Re: [O] [new exporter] 2 questions

Nicolas Goaziou writes: > The parser parses Org syntax. If you see something else, unless there is > an obvious bug, then you are expecting the Org syntax to be different > from what it is. It's even the goal of the parser: to define the way to > read Org syntax. That's what I said. You also defi

Re: [O] [new exporter] 2 questions

Achim Gratz writes: > Nicolas Goaziou writes: >> IMO the parser already DTRT. In which case do you think it doesn't? > DTRT is what you define as DTRT, so yes it does that already. At the > very least it would be nice if the parser warned when it finds stray > syntax pieces that are missing thei

Re: [O] [new exporter] 2 questions

Nicolas Goaziou writes: > IMO the parser already DTRT. In which case do you think it doesn't? DTRT is what you define as DTRT, so yes it does that already. At the very least it would be nice if the parser warned when it finds stray syntax pieces that are missing their match (it took me quite a wh

Re: [O] [new exporter] 2 questions

Bastien writes: > Hi Achim, > > Achim Gratz writes: > >> Nicolas Goaziou writes: It creates this command in the .tex file: \#+begin$_\mathrm{multicols}$ >>> >>> It works here. Difficult to say what is wrong in your buffer without >>> more context. >> >> That result looks exactly l

Re: [O] [new exporter] 2 questions

Hi Achim, Achim Gratz writes: > Nicolas Goaziou writes: >>> It creates this command in the .tex file: >>> >>> \#+begin$_\mathrm{multicols}$ >> >> It works here. Difficult to say what is wrong in your buffer without >> more context. > > That result looks exactly like my problem with multiline \[.

Re: [O] [new exporter] 2 questions

Nicolas Goaziou writes: > henry atting writes: > >> Nicolas Goaziou writes: >> >>> henry atting writes: >>> Here is a minimal example. I use lualatex as tex engine. #+TITLE: lorem ipsum #+LANGUAGE: de #+LaTeX_CLASS: scrartcl #+LaTeX_CLASS_OPTIONS: [DIV=8,a4paper]

Re: [O] [new exporter] 2 questions

Nicolas Goaziou writes: >> It creates this command in the .tex file: >> >> \#+begin$_\mathrm{multicols}$ > > It works here. Difficult to say what is wrong in your buffer without > more context. That result looks exactly like my problem with multiline \[...\], i.e. the parser found something it con

Re: [O] [new exporter] 2 questions

Nicolas Goaziou writes: > henry atting writes: > >> Nicolas Goaziou writes: >>> Try: >>> >>> #+attr_latex: :options "{2}" >>> #+begin_multicols >>> ... >>> #+end_multicols >> >> It creates this command in the .tex file: >> >> \#+begin$_\mathrm{multicols}$ > > It works here. Difficult to

Re: [O] [new exporter] 2 questions

Nicolas Goaziou writes: > henry atting writes: > >> Here is a minimal example. I use lualatex as tex engine. >> >> #+TITLE: lorem ipsum >> #+LANGUAGE: de >> #+LaTeX_CLASS: scrartcl >> #+LaTeX_CLASS_OPTIONS: [DIV=8,a4paper] >> #+LaTeX_HEADER: \usepackage{fontspec} >> >> #+attr_latex: :options "{2

Re: [O] [new exporter] 2 questions

Hi Nicolas, Nicolas Goaziou writes: > Hello, > > henry atting writes: > >> The features are included, does this mean special block should work >> ``out of the box''? If so something like this >> >> #+begin_multicols {2} >> #+end_multicols >> >> should work in LaTeX export (as it did flawlessly

Re: [O] [new exporter] 2 questions

henry atting writes: > Nicolas Goaziou writes: > >> henry atting writes: >> >>> Here is a minimal example. I use lualatex as tex engine. >>> >>> #+TITLE: lorem ipsum >>> #+LANGUAGE: de >>> #+LaTeX_CLASS: scrartcl >>> #+LaTeX_CLASS_OPTIONS: [DIV=8,a4paper] >>> #+LaTeX_HEADER: \usepackage{fontspe

Re: [O] [new exporter] 2 questions

henry atting writes: > Here is a minimal example. I use lualatex as tex engine. > > #+TITLE: lorem ipsum > #+LANGUAGE: de > #+LaTeX_CLASS: scrartcl > #+LaTeX_CLASS_OPTIONS: [DIV=8,a4paper] > #+LaTeX_HEADER: \usepackage{fontspec} > > #+attr_latex: :options "{2}" > #+begin_multicols > > * Lorem ip

Re: [O] [new exporter] 2 questions

henry atting writes: > Nicolas Goaziou writes: >> Try: >> >> #+attr_latex: :options "{2}" >> #+begin_multicols >> ... >> #+end_multicols > > It creates this command in the .tex file: > > \#+begin$_\mathrm{multicols}$ It works here. Difficult to say what is wrong in your buffer without m

Re: [O] [new exporter] 2 questions

Hello, henry atting writes: > The features are included, does this mean special block should work > ``out of the box''? If so something like this > > #+begin_multicols {2} > #+end_multicols > > should work in LaTeX export (as it did flawlessly with the previous > exporter); - but it fails. Try

Re: [O] [New exporter] htmlize included file ?

> #+include: "foo.java" java > > Any obvious reason for this ? > > The reason is really obvious... and to my great shame, I already asked for something similar a couple of months ago. #+include: "foo.java" SRC java I keep finding old blocks without this "src" keyword. Sorry for the noise, Fabr

Re: [O] New exporter - variable name

On Wed, Feb 20, 2013 at 03:24:48PM +0100, itmejl wrote: > > Hi! > > Switching from old to new exporter. > > Using 7.9.3e and Emacs 24.2 on win7. > > Question about variables and name on equivalent vaiables in new exporter. > > Are there new equivalents variables for old variables > org-odt-sty

Re: [O] [new exporter] Guides on what incompatibilities to watch for?

Gunnar Wolf writes: > Hi, > > I'm not very specific in this mail, but am wondering… > > I have some nontrivial documents written in Org-mode. My main use case > for Org is mostly to author texts, rather than using its time-tracking > features. I fear that with the new exporter, several of my docu

Re: [O] [new exporter] Guides on what incompatibilities to watch for?

Hi Suvayu, Suvayu Ali writes: > > > Apart from that I know about the following changes in syntax (to the > best of my knowledge): > 1. Attribute lines now take plists >: #+attr_latex :width "5cm" >: #+attr_beamer :options "width=

Re: [O] [new exporter] Guides on what incompatibilities to watch for?

Gunnar Wolf writes: > Hi, > > I'm not very specific in this mail, but am wondering… > > I have some nontrivial documents written in Org-mode. My main use case > for Org is mostly to author texts, rather than using its time-tracking > features. I fear that with the new exporter, several of my docu

Re: [O] [new exporter] Guides on what incompatibilities to watch for?

On Tue, Feb 19, 2013 at 11:57:03AM -0600, Gunnar Wolf wrote: > Hi, > > I'm not very specific in this mail, but am wondering… > > I have some nontrivial documents written in Org-mode. My main use case > for Org is mostly to author texts, rather than using its time-tracking > features. I fear that

Re: [O] new exporter fails to output footnotes?

Hello, Samuel Wales writes: > Given that it includes things that might change in future versions of > Org, do you think it might be good to separate out the hlevel so that > users don't customize and then find that bugs are introduced because > their customization is out of date? I'm not very f

Re: [O] [New exporter] Should there be an option to kill/exit the dispatcher without using it

Hello, Nicolas, On 2/16/2013 9:09 AM, Nicolas Goaziou wrote: Hello, Charles writes: I'm not sure if my immediate follow up was sent to the list. I forgot about C-g. Charlie Millar On 2/16/2013 8:45 AM, Charles wrote: System Windows 7, 64 bit Emacs 24.2.1 (i386-mingw-nt6.1.7601) of 2012-0

Re: [O] new exporter fails to output footnotes?

On 2/13/13, Nicolas Goaziou wrote: > Samuel Wales writes: >> They are missing from plain text export. > > Fixed too. Thank you. >> In HTML, how do you control the hlevel of the footnotes header? > > See `org-html-footnotes-section'. That looks good. Given that it includes things that might ch

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

Rasmus writes: > Not really. IMO, the old template added to much noise and didn't have > nice defaults. That's purely subjective, though! That's what this thread is for -- collect purely subjective feedback so we can get a rough idea of whether it's useful to implement this feature or not :)

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

Bastien writes: >> It has been removed. Such a template depends on the back-end used, which >> was not the case of the previous implementation. > > One idea would be to have an equivalent of the now-defunct > `org-insert-export-options-template' but for each backend. > > For example `C-c C-e h t'

Re: [O] [New exporter] Should there be an option to kill/exit the dispatcher without using it

Hello, Charles writes: > I'm not sure if my immediate follow up was sent to the list. > > I forgot about C-g. > > Charlie Millar > > On 2/16/2013 8:45 AM, Charles wrote: >> System Windows 7, 64 bit >> Emacs 24.2.1 (i386-mingw-nt6.1.7601) of 2012-08-28 on mRVIN >> Org-mode 7.9.3 (7.9.3e-14-g981c6

Re: [O] [New exporter] Should there be an option to kill/exit the dispatcher without using it

I'm not sure if my immediate follow up was sent to the list. I forgot about C-g. Charlie Millar On 2/16/2013 8:45 AM, Charles wrote: System Windows 7, 64 bit Emacs 24.2.1 (i386-mingw-nt6.1.7601) of 2012-08-28 on mRVIN Org-mode 7.9.3 (7.9.3e-14-g981c6d @ c:/Org/lisp/) It appears that there is

Re: [O] [New exporter] Should there be an option to kill/exit the dispatcher without using it

My mistake. I forgot about C-g. Charlie On 2/16/2013 8:45 AM, Charles wrote: System Windows 7, 64 bit Emacs 24.2.1 (i386-mingw-nt6.1.7601) of 2012-08-28 on mRVIN Org-mode 7.9.3 (7.9.3e-14-g981c6d @ c:/Org/lisp/) It appears that there is no simple option in the export dispatcher to either swit

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

Bastien writes: > Nicolas Goaziou writes: > >> It has been removed. Such a template depends on the back-end used, which >> was not the case of the previous implementation. > > One idea would be to have an equivalent of the now-defunct > `org-insert-export-options-template' but for each backend.

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

Nicolas Goaziou writes: > It has been removed. Such a template depends on the back-end used, which > was not the case of the previous implementation. One idea would be to have an equivalent of the now-defunct `org-insert-export-options-template' but for each backend. For example `C-c C-e h t' w

Re: [O] [New exporter] custom emphasis in org-emphasis-alist

Hi Nicolas, thanks for your replies. I can see that for org syntax stability and to prevent parsing hassle using a variety of characters for emphasis is not desireable. On the other hand, org-emphasis-alist had several advantages that seem not possible with your suggestions. When writing, I

Re: [O] [new exporter] strange behaviour and a question for beamer export

Hello, Eric S Fraga writes: > It would appear, if I understand the documentation in ox-beamer.el > correctly, that an ignoreheading block environment is incompatible with > a column specification. If this is so, it would be nice if the exporter > would indicate an error of some sort or if the b

Re: [O] new exporter fails to output footnotes?

Samuel Wales writes: > Thank you. Confirmed that footnotes are included in HTML now. > > They are missing from plain text export. Fixed too. > In HTML, how do you control the hlevel of the footnotes header? See `org-html-footnotes-section'. > Also, there is a formatting issue with footnotes.

Re: [O] [new exporter] workaround/replacement for org-export-as-html-batch

On Tue, 12 Feb 2013 20:34:55 +0100 Nicolas Goaziou wrote: > Does `org-html-export-to-html' works as a replacement for > `org-export-as-html-batch'? Yes! Thank you so much! Detlef

Re: [O] [new exporter] strange behaviour and a question for beamer export

Eric S Fraga writes: [...] > The problem is annoyingly non-reproducible on demand! A block that I > have indicated should be in a column, e.g.: > > #+begin_src org > *** gui :BMCOL:B_ignoreheading: > :PROPERTIES: > :BEAMER_col: 0.25 > :BEAMER_env: ignorehead

Re: [O] [new exporter] strange behaviour and a question for beamer export

Eric S Fraga writes: [...] > I also have a simple question that I'm sure has been answered in this > list but I've not yet found the answer and apologies for that: how do I > add options to the \begin{frame} line, such as [shrink=10] say? I have > tried the BEAMER_envargs property and also #+AT

Re: [O] [new exporter] workaround/replacement for org-export-as-html-batch

Hello, Detlef Steuer writes: > I rely on > > emacs --batch \ > --eval "(add-to-list 'load-path \"${HOME}/GIT/org-mode/lisp/\")"\ > --load ${HOME}/GIT/org-mode/lisp/org.el \ > --visit file.org \ > --funcall org-export-as-html-batch > > somewhere in my HTML generating workf

Re: [O] new exporter fails to output footnotes?

On 2/11/13, Nicolas Goaziou wrote: > It should be fixed in master. Could you confirm it? Thank you. Confirmed that footnotes are included in HTML now. They are missing from plain text export. In HTML, how do you control the hlevel of the footnotes header? Also, there is a formatting issue wit

Re: [O] New exporter macro question

Hello Nicolas, thanks for your reply. I now remember this point of downgrading the macros and replacing complex macro calls with babel code. Thanks also for the easy work-around. - Carsten On 11.2.2013, at 22:37, Nicolas Goaziou wrote: > Hello, > > Carsten Dominik writes: > >> I am port

Re: [O] New exporter macro question

Hello, Carsten Dominik writes: > I am porting my websites to the new exporter, finally. Much is very smooth. > I do have a problem with macros: > > > * Macro definition > > >#+MACRO: thumbright #+ATTR_HTML: style="float:right;width:$1;margin:0px > 20px 0px 20px;" \n [[./Content/$2/t

Re: [O] new exporter fails to output footnotes?

Samuel Wales writes: > Surely this is pilot error someplace. > > (org-export-to-buffer > 'html > (get-buffer-create "test") > t > nil > t) > > *** test > asasdf[fn::test] > > *** output > > asasdf href="#fn.1">1 It should be fixed in master. Cou

Re: [O] New exporter macro question

Nick Dokos wrote: > Carsten Dominik 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 wi

Re: [O] New exporter macro question

Carsten Dominik wrote: > > On 11 feb. 2013, at 13:48, Carsten Dominik wrote: > > > > > Hi, > > > > I am porting my websites to the new exporter, finally. Much is very > > smooth. I do have a problem with macros: > > > > > > * Macro definition > > > > > > #+MACRO: thumbright #+ATTR_H

Re: [O] New exporter macro question

On 11 feb. 2013, at 13:48, Carsten Dominik wrote: > > Hi, > > I am porting my websites to the new exporter, finally. Much is very smooth. > I do have a problem with macros: > > > * Macro definition > > > #+MACRO: thumbright #+ATTR_HTML: style="float:right;width:$1;margin:0px > 20px 0

Re: [O] new exporter fails to output footnotes?

Samuel Wales writes: > On 2/10/13, Nicolas Goaziou wrote: >> For now, you can't, but that's a problem. I think the framework needs >> a step before the template function, in order to add some persistent >> data, even in case of a body-only export. > > Thank you for the answer. > > Is there a way

Re: [O] new exporter fails to output footnotes?

On 2/10/13, Nicolas Goaziou wrote: > For now, you can't, but that's a problem. I think the framework needs > a step before the template function, in order to add some persistent > data, even in case of a body-only export. Thank you for the answer. Is there a way to run the old exporter then? I'

Re: [O] new exporter fails to output footnotes?

Samuel Wales writes: > On 2/10/13, Nicolas Goaziou wrote: >> I assume you wonder why there's no footnote definition. That's because >> this is a body-only export. Footnote definitions belong to the global >> template, which is ignored when this option is active. > > Why would you not want footno

Re: [O] new exporter fails to output footnotes?

On 2/10/13, Nicolas Goaziou wrote: > Beware, `org-export-to-buffer' expects a string as its second argument, Will fix thanks. > I assume you wonder why there's no footnote definition. That's because > this is a body-only export. Footnote definitions belong to the global > template, which is igno

Re: [O] new exporter fails to output footnotes?

Hello, Samuel Wales writes: > Surely this is pilot error someplace. > > (org-export-to-buffer > 'html > (get-buffer-create "test") > t > nil > t) > Beware, `org-export-to-buffer' expects a string as its second argument, not a buffer. So: (org

Re: [O] [New exporter] custom emphasis in org-emphasis-alist

Completing myself, > On the other hand, you may be able to parse custom markup with the help > of a filter: > > #+begin_src emacs-lisp > (defun my-special-markup (text backend info) > (when (and (org-export-derived-backend-p backend 'html) > (string-match "\\([ ('\"{]\\|^\\)\\(

Re: [O] [New exporter] custom emphasis in org-emphasis-alist

Hello, Gregor Kappler writes: > I am currently migrating my system and contribute my first stop: > custom emphasis characters that I use extensively: > - "!" is used for exclamations, > - "?" for questions, and > - "#" for in-text comments that I do not want exported. Emphasis characters are no

Re: [O] [New exporter] custom emphasis in org-emphasis-alist

Gregor Kappler writes: > Cudos for all the work that has been done on migrating to the new > exporter. I so welcome that exporting now is approaching a clean > design! Let me join my voice to the chorus! Munch congratulations, and thanks! There is an impressive amount of work in all this, it h

Re: [O] [New exporter] Key bindings and typographical error

"Sebastien Vauban" writes: > Hi Eric, > >> >> and I would also like to take this opportunity to suggest a change in >> the interface. >> >> Given that we have moved to a multi-key sequence for selecting exporter >> and then action, could these two aspects not be dealt with in the >> mini-buffer?

Re: [O] [New exporter] Key bindings and typographical error

Sebastien Vauban writes: > Are you aware of: > > (setq org-export-dispatch-use-expert-ui t) > > If not, well, you should -- at least from now on! I wasn't but I am now! I guess I shouldn't be surprised that this exists, just annoyed with myself for not thinking that there would be such a vari

Re: [O] [New exporter] Key bindings and typographical error

Charles Berry writes: > If you customize org-export-dispatch-use-expert-ui to t Ah! Thanks. Missed this. > Then you will get the minibuffer, albeit with less verbose prompts than you > describe. Yes. Definitely tests the memory ;-) Thanks again, eric -- : Eric S Fraga, GnuPG: 0xC89193D8FF

Re: [O] [New exporter] Key bindings and typographical error

Hello, "Sebastien Vauban" writes: > While using the new dispatcher, I'd like to propose some adaptations -- before > it's too late (before everybody gets accustomed to your new bindings). [...] > In summary: > - Use "As ... buffer/file" writing > - Use key `b' for "buffer" result (for both H

Re: [O] New exporter, beamer confusion

Rasmus writes: >> There is the #+LATEX_HEADER:. Is a keyword specific to Beamer >> required? It would by symmetric with #+BEAMER: but I have never >> needed it before. > > > Something like > > #+LATEX_HEADER:\AtBeginSection[]{\frame{\thispagestyle{empty}\tableofcontents[currentsection]}} > > is

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

Hello, Rick Frankel writes: > Been using the new exporter for a while, and have not had much problem > w/ the migration, but it seems that org-insert-export-options-template > and the associated keybinding in the dispatch menu are gone. > > Once the old exporter (org-exp.el) is entirely gone, i

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

> Been using the new exporter for a while, and have not had much problem > w/ the migration, but it seems that org-insert-export-options-template > and the associated keybinding in the dispatch menu are gone. > > Once the old exporter (org-exp.el) is entirely gone, it's going to be > real difficu

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

Hello, Charles Berry writes: > 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. Docstring fixed. Thank you. Regards, -- Nicol

Re: [O] [New exporter] Key bindings and typographical error

Suvayu Ali gmail.com> writes: > > Hi Eric and Seb, > > On Sat, Feb 09, 2013 at 12:28:06AM +1030, Eric S Fraga wrote: > > > > Given that we have moved to a multi-key sequence for selecting exporter > > and then action, could these two aspects not be dealt with in the > > mini-buffer? If you

Re: [O] [New exporter] Key bindings and typographical error

Hi Eric, Eric S Fraga wrote: >> While using the new dispatcher, I'd like to propose some adaptations -- >> before >> it's too late (before everybody gets accustomed to your new bindings). > > and I would also like to take this opportunity to suggest a change in > the interface. > > Given that we

Re: [O] [New exporter] Key bindings and typographical error

Hi Eric and Seb, On Sat, Feb 09, 2013 at 12:28:06AM +1030, Eric S Fraga wrote: > > Given that we have moved to a multi-key sequence for selecting exporter > and then action, could these two aspects not be dealt with in the > mini-buffer? I find the display of all the options confusing... I > wo

Re: [O] [New exporter] Key bindings and typographical error

Sebastien Vauban writes: > While using the new dispatcher, I'd like to propose some adaptations -- before > it's too late (before everybody gets accustomed to your new bindings). and I would also like to take this opportunity to suggest a change in the interface. Given that we have moved to a m

Re: [O] New exporter, beamer confusion

Nicolas Goaziou writes: >> Should there be a check in the exporter, for latex based backends, if >> the document class expected is not defined? This would have made things >> a lot quicker to resolve in this case! > > What is an "expected document class"? Beamer export can happen with > a "beame

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

Sebastien Vauban writes: > > Hello Nicolas, > > I'm still searching which variables now host the following customizations: > > --8<---cut here---start->8--- > ;; markup for TODO keywords, as a printf format > (setq org-export-latex-todo-keyword-markup "\\col

Re: [O] New exporter, beamer confusion

Nicolas, > There is the #+LATEX_HEADER:. Is a keyword specific to Beamer > required? It would by symmetric with #+BEAMER: but I have never > needed it before. Something like #+LATEX_HEADER:\AtBeginSection[]{\frame{\thispagestyle{empty}\tableofcontents[currentsection]}} is not interesting to

Re: [O] New exporter, beamer confusion

Hello, Rasmus writes: > Nicolas Goaziou writes: > >> If the author is cautious about keywords used (i.e. #+BEAMER: or >> #+LATEX:), it should be possible to export the same document with either >> `beamer' or `latex' back-end. Though, I don't know how much difference >> there would be between t

Re: [O] New exporter, beamer confusion

Nicolas Goaziou writes: > If the author is cautious about keywords used (i.e. #+BEAMER: or > #+LATEX:), it should be possible to export the same document with either > `beamer' or `latex' back-end. Though, I don't know how much difference > there would be between the output from `latex' and a Bea

Re: [O] [New exporter] Error: (wrong-type-argument stringp nil)

"Sebastien Vauban" writes: > Trying to convert some more files (to HTML) with the new exporter, I did a > test with the following one: Fixed, thanks. -- Bastien

Re: [O] New exporter, beamer confusion

Vincent Beffara writes: > Sure, it should be in the default list. What is the drawback? The default list is defined in ox-latex.el, which doesn't know anything about ox-beamer.el. The drawback is that it doesn't seem clean to me. I think it's better to make it a fallback value hardcoded (or in

Re: [O] New exporter, beamer confusion

Hi, > LaTeX class is never unspecified because `beamer' back-end is > a derivative of `latex', and, as such, `org-latex-default-class' will be > used. `beamer' could specify its own default class, but that class would > still need to be defined in `org-latex-classes'. Sure, it should be in the de

Re: [O] new exporter - LaTeX export setting org-export-latex-packages-alist and BUG empty source block export

Rainer M Krug writes: > One observation though: I updated and compiled org while emacs was running, > then reloaded it and > tried the export of the empty souce block, and the error was still there > although emacs told me > that I had successfully loaded the new version. > > I restarted emacs,

Re: [O] new exporter - LaTeX export setting org-export-latex-packages-alist and BUG empty source block export

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/02/13 14:37, Nicolas Goaziou wrote: > Hello, > > Rainer M Krug writes: > >> Hi >> >> I had the following in my emacs.org: >> >> #+begin_src emacs-lisp (require 'org-latex) (setq org-export-latex-listings >> t) (add-to-list >> 'org-export-l

Re: [O] new exporter - LaTeX export setting org-export-latex-packages-alist and BUG empty source block export

Hello, Rainer M Krug writes: > Hi > > I had the following in my emacs.org: > > #+begin_src emacs-lisp > (require 'org-latex) > (setq org-export-latex-listings t) > (add-to-list 'org-export-latex-packages-alist '("" "listings")) > (add-to-list 'org-export-latex-packages-alist '("" "color"

Re: [O] New exporter, beamer confusion

> Should there be a check in the exporter, for latex based backends, if > the document class expected is not defined? This would have made things > a lot quicker to resolve in this case! What is an "expected document class"? Beamer export can happen with a "beamer" or an "article" (and probably o

Re: [O] New exporter, beamer confusion

On Feb 7, 2013 3:57 AM, "Nicolas Goaziou" wrote: > > Btw, *who* preferred \alert? (Orwell, Politics and the English Language: > > "Never use the passive [voice] where you can use the active.") > > Obviously, me, as the author of the back-end. Org offers only one slot > for "strong emphasis". I had

Re: [O] New exporter, beamer confusion

Nicolas Goaziou writes: > Hello, > > Eric S Fraga writes: > >> Taking your updated version of the example document, I cannot get the >> exporter to generate a latex file that will compile because it is >> missing a documentclass directive. Is there something else that needs >> to be configured

Re: [O] New exporter, beamer confusion

James Harkins writes: > Btw, *who* preferred \alert? (Orwell, Politics and the English Language: > "Never use the passive [voice] where you can use the active.") Obviously, me, as the author of the back-end. Org offers only one slot for "strong emphasis". I had to choose between bold and alert,

Re: [O] New exporter, beamer confusion

Hello, Eric S Fraga writes: > Taking your updated version of the example document, I cannot get the > exporter to generate a latex file that will compile because it is > missing a documentclass directive. Is there something else that needs > to be configured to support beamer, as in maybe org-e

Re: [O] New exporter, beamer confusion

Hi Rasmus, Rasmus wrote: > James Harkins writes: > >> Btw, *who* preferred \alert? (Orwell, Politics and the English Language: >> "Never use the passive [voice] where you can use the active.") > > I prefer alert. See the Beamer manual (texdoc beamer in texlive) on > change of style and how to us

Re: [O] New exporter, beamer confusion

On Wed, Feb 06, 2013 at 01:32:22PM +0100, Rasmus wrote: > > I don't know how hard it would be to make the "default" block (of > level 3, say) a list block, but I guess that's ultimately what you > want? Such a behavior shouldn't be the default, IMO, since a headline > is not a list. > Nested he

Re: [O] New exporter, beamer confusion

James Harkins writes: > Btw, *who* preferred \alert? (Orwell, Politics and the English Language: > "Never use the passive [voice] where you can use the active.") I prefer alert. See the Beamer manual (texdoc beamer in texlive) on change of style and how to use alert (e.g. alert on one particula

Re: [O] New exporter, beamer confusion

James Harkins writes: [...] > Ok. There was something about customizing this on the list just recently. > I'll use that. (FWIW, I had to produce a number of *gasp cough choke* > PowerPoint shows in my previous job, and they told us not to use red for > *anything* unless it really was a four-alar

Re: [O] New exporter, beamer confusion

Thanks for all this. I'll look at the new org markup later today. That should help a lot. On Feb 6, 2013 3:03 AM, "Nicolas Goaziou" wrote: > > 3. Strong *emphasis* now renders in red, instead of keeping the text's > > original color and switching to boldface. > > Indeed. Strong emphasis in Beamer

Re: [O] New exporter, beamer confusion

Nicolas Goaziou writes: [...] > Let's start slowly. I think you can get how to make the changes yourself > with a couple of examples. Since you seem to like lists (you know that > Till Tantau frowns upon the use of third level lists in presentations, > don't you?), the first rule to know is: [.

Re: [O] New exporter, beamer confusion

Nicolas Goaziou writes: [...] >> I have attached the simple test file. >> >> Where am I going wrong? If I change H:2 to H:1, it works although >> obviously the output is not what I want. Have I misunderstand something >> rather fundamental? > > I have no problem exporting this file. Though, j

Re: [O] New exporter, beamer confusion

Hello, > I'm attaching an org file that illustrates a couple of the beamer > formatting options that I used a lot in the old exporter. See below. > 1. I *did* use the block environment to emphasize some text by pulling > it out of the "itemize" bullet lists. If I customize blockenv in org > to

Re: [O] New exporter, beamer confusion

Hello, Eric S Fraga writes: > I have decided to bite the bullet and try to get all of my beamer files > working with the new exporter. I have started simply with the > presentation.org file that I had put on Worg for the tutorial on beamer > for the old exporter. > > A truncated version of that

Re: [O] New exporter, beamer confusion

James Harkins wrote: > ... > > I get the feeling here that the new beamer exporter was written > without a lot of real-world user requirements. Certainly, it's > understandable that HTML, LaTeX article-style and ODT exporters would > be more widely used and more important to get right first. Fo

<    1   2   3   4   5   6   >