Hello,
tftor...@tftorrey.com (T.F. Torrey) writes:
One small problem, though: I see that if there is a TOC at the top and
then one included later using #+TOC, the exporter gives them both the
same id (div id=table-of-contents). Duplicate ID's makes the XML
invalid.
What do you suggest
Hi Nicolas,
I have scripted an ical export that invokes:
org-icalendar-combine-agenda-files
but the thing fails on my server and home boxes. I investigated and
found that a misguided babel block I added in a hurry and forgot about
was causing trouble:
#+BEGIN_SRC xml
#+END_SRC
It seems
Hello,
Simon Thum simon.t...@gmx.de writes:
I have scripted an ical export that invokes:
org-icalendar-combine-agenda-files
but the thing fails on my server and home boxes. I investigated and
found that a misguided babel block I added in a hurry and forgot about
was causing trouble:
We were talking about the HTML for footnote definitions.
On 2/13/13, Nicolas Goaziou n.goaz...@gmail.com wrote:
Anyway, if you send the correct HTML that should be generated, I will
fix it.
Probably all that needs to be done is to not use a table. I tested this by
manually removing table td
On 2/27/13, Samuel Wales samolog...@gmail.com wrote:
I tested it in Firefox and w3m.
It solves the problem and it seems reasonably good to me.
Samuel
--
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
The disease DOES progress. MANY people have died from it. ANYBODY
can get it.
Myles English mylesengl...@gmail.com writes:
Thanks for looking at this, I tried just now and can't see any change in
what I reported above.
Since the patch, \[ \mysymbol = f \] is correctly displayed after C-c
C-x C-l here (I just changed ~/bug with bug as bug.sty is not
located in my home
Nicolas Goaziou writes:
Myles English mylesengl...@gmail.com writes:
Thanks for looking at this, I tried just now and can't see any change in
what I reported above.
Since the patch, \[ \mysymbol = f \] is correctly displayed after C-c
C-x C-l here (I just changed ~/bug with bug as bug.sty
Hi Myles,
Myles English mylesengl...@gmail.com writes:
#+LATEX_HEADER: \usepackage{~/bug}
you want
#+LATEX_HEADER: \usepackage{/full/path/bug}
HTH,
--
Bastien
Bastien writes:
Hi Myles,
Myles English mylesengl...@gmail.com writes:
#+LATEX_HEADER: \usepackage{~/bug}
you want
#+LATEX_HEADER: \usepackage{/full/path/bug}
I do use the full path but cut it down for the example, which was
incorrect, because it should have had a full path, so thanks
Hi Myles,
I followed the directions. I created bug.sty and minimal.el in the
same directory and it worked for me.
My ox.elc was in /home/evan/Documents/org/elisp/org-mode.
My bug.sty was in /home/evan/Documents/org/exporter
My minimal.el was in /home/evan/Documents/org/exporter
My bug.org was
Hi Evan,
Evan Misshula writes:
I followed the directions. I created bug.sty and minimal.el in the
same directory and it worked for me.
My ox.elc was in /home/evan/Documents/org/elisp/org-mode.
My bug.sty was in /home/evan/Documents/org/exporter
My minimal.el was in
If it would be helpful I can send a screen shot to anyone who wants one offlist.
Best,
Evan
On Tue, Feb 26, 2013 at 9:54 AM, Evan Misshula evanmissh...@gmail.com wrote:
Hi Myles,
I followed the directions. I created bug.sty and minimal.el in the
same directory and it worked for me.
My
Since the last pull (release_7.9.3f-1205-g0030e1) headlines are exported
to LaTeX like this:
\subsection*[Headline]{Headline}
which does not produce proper headlines in the resulting pdf.
Regards,
--
henry, web: http://literaturlatenight.de
Hello,
henry atting s...@online.de writes:
Since the last pull (release_7.9.3f-1205-g0030e1) headlines are exported
to LaTeX like this:
\subsection*[Headline]{Headline}
which does not produce proper headlines in the resulting pdf.
It should be fixed now. Thank you.
Regards,
--
Nicolas
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
henry atting s...@online.de writes:
Since the last pull (release_7.9.3f-1205-g0030e1) headlines are exported
to LaTeX like this:
\subsection*[Headline]{Headline}
which does not produce proper headlines in the resulting pdf.
It should
Hello Bastien,
Bastien wrote:
Nicolas Goaziou n.goaz...@gmail.com 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
Hello,
Sebastien Vauban
wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org writes:
Hello Bastien,
Bastien wrote:
Nicolas Goaziou n.goaziou-re5jqeeqqe8avxtiumw...@public.gmane.org writes:
It has been removed. Such a template depends on the back-end used, which
was not the case of the
Hello,
Myles English mylesengl...@gmail.com writes:
I have a problem where org-preview-latex-fragment appears not to use a
style file the latex header.
Starting emacs like this:
emacs -Q -l ~/minimal.el ~/file.org
When I export the whole buffer to pdf it looks right.
When I call
I'm trying to html export my babel'd config. It seems to be choking on some
of the larger blocks (300+ lines) of code (offending blocks seem to be org,
erc, programming config). I should probably chop these down a bit for
readability (still working on finshing org-ifying it), but I'd also figure
Hello,
Kyle Machulis k...@nonpolynomial.com writes:
I'm trying to html export my babel'd config. It seems to be choking on some
of the larger blocks (300+ lines) of code (offending blocks seem to be org,
erc, programming config). I should probably chop these down a bit for
readability (still
Just tested it, works now. Thanks! :D
On Mon, Feb 25, 2013 at 3:31 PM, Nicolas Goaziou n.goaz...@gmail.comwrote:
Hello,
Kyle Machulis k...@nonpolynomial.com writes:
I'm trying to html export my babel'd config. It seems to be choking on
some
of the larger blocks (300+ lines) of code
Hey Seb,
On Mon, Feb 25, 2013 at 02:15:05PM +0100, Sebastien Vauban wrote:
PS- By the way, there is already such a sort of template for Beamer...
I believe Nicolas' argument was, for the new exporter such a template
depends on the backend hence a default one for beamer makes sense but
not a
Nicolas Goaziou writes:
I have a problem where org-preview-latex-fragment appears not to use a
style file the latex header.
Starting emacs like this:
emacs -Q -l ~/minimal.el ~/file.org
When I export the whole buffer to pdf it looks right.
When I call org-preview-latex-fragment on the
Achim Gratz strom...@nexgo.de 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
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 faults
Nicolas-
The new HTML exporter does not actually use the value of the
:HTML_CONTAINER_CLASS: property. The old exporter saved the value off
into the property :html-container-class on the headline (with
`org-export-remember-html-container-classes'), the new exporter
references the
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.
Starting emacs like this:
emacs -Q -l ~/minimal.el ~/file.org
When I export the whole buffer to pdf it looks
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.
Starting
Hi Rick,
Rick Frankel r...@rickster.com 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))
Hi Achim,
Achim Gratz strom...@nexgo.de 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
Bastien b...@altern.org writes:
Hi Achim,
Achim Gratz strom...@nexgo.de 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
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
Achim Gratz strom...@nexgo.de 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
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 defined
Achim Gratz strom...@nexgo.de 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
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,
Achim Gratz strom...@nexgo.de 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
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
Achim Gratz strom...@nexgo.de 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
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 of
I'm checking out the new exporter. After some configuration and file
changes it works now, could be worse.
http://article.gmane.org/gmane.emacs.orgmode/65574 says:
The `org-special-blocks.el' library, which has been moved to “contrib/”,
is obsolete since its features are included in the new
Hello,
henry atting s...@online.de 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
henry atting s...@online.de writes:
Nicolas Goaziou n.goaz...@gmail.com 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
henry atting s...@online.de 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
henry atting s...@online.de writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
henry atting s...@online.de 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]
Hi Nicolas,
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
henry atting s...@online.de 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
Nicolas Goaziou n.goaz...@gmail.com writes:
henry atting s...@online.de 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}
Nicolas Goaziou n.goaz...@gmail.com writes:
henry atting s...@online.de writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
Try:
#+attr_latex: :options {2}
#+begin_multicols
...
#+end_multicols
It creates this command in the .tex file:
\#+begin$_\mathrm{multicols}$
It works
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 considers
Nicolas Goaziou n.goaz...@gmail.com writes:
henry atting s...@online.de writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
henry atting s...@online.de writes:
Here is a minimal example. I use lualatex as tex engine.
#+TITLE: lorem ipsum
#+LANGUAGE: de
#+LaTeX_CLASS: scrartcl
Hi,
I have a problem with htmlize.
I'm running the very latest trunk version of org-mode.
If I write an src block code with :
#+begin_src java
...
#+end_src
I get htmlized output.
But it does not work with :
#+include: foo.java java
Any obvious reason for this ?
Thanks for any help,
--
#+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,
Fabrice
Gunnar Wolf gw...@gwolf.org 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
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-styles-dir, org-export-odt-styles-file and those for schema-dir?
Thanks in
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-styles-dir,
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 documents'
features will no longer
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 with
Gunnar Wolf gw...@gwolf.org 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
Hi Suvayu,
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
http://orgmode.org/worg/org-faq.html#new-exporter-switch
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
Hello,
Samuel Wales samolog...@gmail.com 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
Nicolas Goaziou n.goaz...@gmail.com 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
Bastien b...@altern.org writes:
Nicolas Goaziou n.goaz...@gmail.com 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
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 switch to and then kill or simply kill the export dispatcher UI
(or buffer) if
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
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
Hello,
Charles mill...@verizon.net 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
Bastien b...@altern.org 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
Rasmus ras...@gmx.us 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
On 2/13/13, Nicolas Goaziou n.goaz...@gmail.com wrote:
Samuel Wales samolog...@gmail.com 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
Hello, Nicolas,
On 2/16/2013 9:09 AM, Nicolas Goaziou wrote:
Hello,
Charles mill...@verizon.net 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
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
On Tue, 12 Feb 2013 20:34:55 +0100
Nicolas Goaziou n.goaz...@gmail.com wrote:
Does `org-html-export-to-html' works as a replacement for
`org-export-as-html-batch'?
Yes! Thank you so much!
Detlef
Samuel Wales samolog...@gmail.com 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
Hello,
Eric S Fraga e.fr...@ucl.ac.uk 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
Dear all,
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 workflow.
I see org-export-as-html-batch in
On 2/11/13, Nicolas Goaziou n.goaz...@gmail.com 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
Hello,
Detlef Steuer detlef.ste...@gmx.de 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
Hello,
I am giving a presentation tomorrow. I am not panicked because I have a
PDF of my presentation generated using the old exporter a couple of
weeks ago. However, as a stress test, I thought I would try to convert
this presentation to work with the new exporter. I have run into a
problem.
Eric S Fraga e.fr...@ucl.ac.uk 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
Eric S Fraga e.fr...@ucl.ac.uk 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:
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
0px 20px; \n [[./Content/$2/thumb.jpg]]
* Macro call
On 11 feb. 2013, at 13:48, Carsten Dominik carsten.domi...@gmail.com 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:
Carsten Dominik carsten.domi...@gmail.com wrote:
On 11 feb. 2013, at 13:48, Carsten Dominik carsten.domi...@gmail.com 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
Nick Dokos nicholas.do...@hp.com wrote:
Carsten Dominik carsten.domi...@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.
Samuel Wales samolog...@gmail.com writes:
Surely this is pilot error someplace.
(org-export-to-buffer
'html
(get-buffer-create test)
t
nil
t)
*** test
asasdf[fn::test]
*** output
p
asasdfsupa id=fnr.1 name=fnr.1 class=footref
Hello,
Carsten Dominik carsten.domi...@gmail.com 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
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 n.goaz...@gmail.com wrote:
Hello,
Carsten Dominik
Hello,
Gregor Kappler g.kapp...@gmx.net 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
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 \\([
Hello,
Samuel Wales samolog...@gmail.com 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.
On 2/10/13, Nicolas Goaziou n.goaz...@gmail.com 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
Samuel Wales samolog...@gmail.com writes:
On 2/10/13, Nicolas Goaziou n.goaz...@gmail.com 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.
On 2/10/13, Nicolas Goaziou n.goaz...@gmail.com 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
Samuel Wales samolog...@gmail.com writes:
On 2/10/13, Nicolas Goaziou n.goaz...@gmail.com 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
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!
I am currently migrating my system and contribute my first stop:
custom emphasis characters that I use extensively:
- ! is used for exclamations,
- ? for
Gregor Kappler g.kapp...@gmx.net 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
Nicolas Goaziou n.goaz...@gmail.com 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
Sebastien Vauban wxhgmqzgw...@spammotel.com 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
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
would
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 have moved
201 - 300 of 685 matches
Mail list logo
