Suvayu Ali fatkasuvayu+linux at gmail.com writes:
On Mon, Feb 04, 2013 at 12:00:08PM +0800, James Harkins wrote:
#+OPTIONS: H:10 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t :t
The H:10 is your problem. Since you want 2nd level headlines to be
frames, it should be H:2.
Ah. OK, that's
Hello,
James Harkins jamshar...@gmail.com writes:
Suvayu Ali fatkasuvayu+linux at gmail.com writes:
On Mon, Feb 04, 2013 at 12:00:08PM +0800, James Harkins wrote:
#+OPTIONS: H:10 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t :t
The H:10 is your problem. Since you want 2nd level
On Feb 5, 2013 3:51 AM, Nicolas Goaziou n.goaz...@gmail.com wrote:
In particular, All frames children become block environments. So in
your example Third-level is a block environment and Fourth-level is
a block within it. There's no flattening going on (look at the tex file
to convince
James Harkins jamshar...@gmail.com wrote:
On Feb 5, 2013 3:51 AM, Nicolas Goaziou n.goaz...@gmail.com wrote:
In particular, All frames children become block environments. So in
your example Third-level is a block environment and Fourth-level is
a block within it. There's no flattening
On Mon, Feb 04, 2013 at 12:00:08PM +0800, James Harkins wrote:
#+OPTIONS: H:10 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t :t
The H:10 is your problem. Since you want 2nd level headlines to be
frames, it should be H:2.
Hope this helps,
--
Suvayu
Open source is the future. It sets us
Hello,
Bastien b...@altern.org writes:
Though, I think I have to withdraw my proposal about using #+DATE: value
as a time format string. Indeed, date value, along with any document
property, is parsed, which defeats the purpose of using it as a format
string.
We can still implement a
Nicolas Goaziou n.goaz...@gmail.com writes:
q
Hello,
Bastien b...@altern.org writes:
Though, I think I have to withdraw my proposal about using #+DATE:
value
as a time format string. Indeed, date value, along with any
document
property, is parsed, which defeats the purpose of using it as
Hello,
Jambunathan K kjambunat...@gmail.com writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
Jambunathan K kjambunat...@gmail.com writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
#+begin_src emacs-lisp
(defun my-options-change-fun (tree backend info)
(when
Hello,
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Sorry for hijacking this thread. But I am also interested in backend
specific options. Could you give an example of how to achieve something
like this with the new exporter:
#+begin_src R :results graphics :file (if (and
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
Ezequiel Birman stormwa...@espiga4.com.ar writes:
Is it possible to write something like this with the new exporter?
#+OPTIONS: (if (and (boundp 'org-export-current-backend) (eq
org-export-current-backend 'e-beamer)) H:1 H:3)
There is
Hello,
cbe...@tajo.ucsd.edu writes:
'backend' is in the scope of transcoding functions like
inline-src-block.
I am currently taking advantage of this, but it is a shortcut rather
than a necessity.
Is your advice Don't do that ?
I would rather say Don't do that in public code. There's no
Hi Nicolas,
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
Ezequiel Birman stormwa...@espiga4.com.ar writes:
Is it possible to write something like this with the new exporter?
#+OPTIONS: (if (and (boundp 'org-export-current-backend) (eq
org-export-current-backend 'e-beamer)) H:1
Jambunathan K kjambunat...@gmail.com writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
#+begin_src emacs-lisp
(defun my-options-change-fun (tree backend info)
(when (org-export-derived-backend-p backend 'e-beamer)
(plist-put info :with-author nil))
;; Don't forget to return tree.
Nicolas Goaziou n.goaz...@gmail.com writes:
Jambunathan K kjambunat...@gmail.com writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
#+begin_src emacs-lisp
(defun my-options-change-fun (tree backend info)
(when (org-export-derived-backend-p backend 'e-beamer)
(plist-put info
Hello,
Ezequiel Birman stormwa...@espiga4.com.ar writes:
Is it possible to write something like this with the new exporter?
#+OPTIONS: (if (and (boundp 'org-export-current-backend) (eq
org-export-current-backend 'e-beamer)) H:1 H:3)
There is no `org-export-current-backend' in the new
Nicolas == Nicolas Goaziou n.goaz...@gmail.com writes:
Hello, Ezequiel Birman stormwa...@espiga4.com.ar writes:
Is it possible to write something like this with the new
exporter?
#+OPTIONS: (if (and (boundp 'org-export-current-backend) (eq
Nicolas Goaziou n.goaz...@gmail.com writes:
#+begin_src emacs-lisp
(defun my-options-change-fun (tree backend info)
(when (org-export-derived-backend-p backend 'e-beamer)
(plist-put info :with-author nil))
;; Don't forget to return tree.
tree)
CAVEAT: plist-put can return a
Aloha James,
James Harkins jamshar...@gmail.com writes:
I apologize in advance for what is likely to be a dumb question, but
I'm struggling to find documentation of the new exporter. Google
pointed to [1], but this is documentation for developers of new
backends. I only want to use the
James Harkins jamshar...@gmail.com writes:
Specific question: Is there an easy way to use a given LaTeX template (.cls
and .bib)? (I also found [2] but easy is not how I would describe that.)
The easiest way is probably
#+BEGIN_SRC emacs-lisp
(require 'org-export)
(require 'org-e-latex)
On Jan 18, 2013 4:11 PM, Florian Beck f...@miszellen.de wrote:
James Harkins jamshar...@gmail.com writes:
Specific question: Is there an easy way to use a given LaTeX template
(.cls and .bib)? (I also found [2] but easy is not how I would describe
that.)
The easiest way is probably
... snip
Bastien b...@altern.org writes:
I agree they are general and should be move out of org-export.el.
Note that one of my plan for 8.[01] is to put org.el on diet so that
it loads more quickly and for more basic stuff. So maybe there will
be org-plan.el at some point for org-schedule,
Hi Nicolas,
Nicolas Goaziou n.goaz...@gmail.com writes:
The attached patch moves them into org.el, with an org-timestamp-
prefix.
Looks, good, please go ahead.
Though, I think I have to withdraw my proposal about using #+DATE: value
as a time format string. Indeed, date value, along with
Hello,
Ista Zahn istaz...@gmail.com writes:
Does the new exporter have any equivalent of
org-export-latex-verbatim-wrap? I've looked but don't see anything.
How can I format verbatim output when using the new exporter?
Add a filter to `org-export-filter-fixed-width-functions'. E.g.:
Hello,
Bastien b...@altern.org writes:
Though it may be the job of back-ends to provide such a variable
variable, whenever it makes sense.
Yes, I think it's the job of backends.
For example, in the `e-latex' back-end, there is
`org-e-latex-date-format'.
Should the value of the variable be
Hi Nicolas,
Nicolas Goaziou n.goaz...@gmail.com writes:
For example, in the `e-latex' back-end, there is
`org-e-latex-date-format'.
Should the value of the variable be used as an argument for
`org-export-format-timestamp' if the #+DATE: keyword only contains
a timestamp object, and for
Bastien b...@altern.org writes:
Should the value of the variable be used as an argument for
`org-export-format-timestamp' if the #+DATE: keyword only contains
a timestamp object, and for `format-time-string' otherwise?
Yes, good idea!
Ok.
Before I start coding it, I wonder if functions
Hi Nicolas,
Nicolas Goaziou n.goaz...@gmail.com writes:
Before I start coding it, I wonder if functions related to timestamp
objects, that is `org-export-timestamp-has-time-p',
`org-export-format-timestamp', `org-export-split-timestamp-range' and
`org-export-translate-timestamp' shouldn't be
Hello,
Bastien b...@altern.org writes:
Rasmus ras...@gmx.us writes:
Would it be desirable if the new exporter took the variable
org-export-date-timestamp-format into consideration when formatting
dates?
I think so. What do you think, Nicolas?
I'm not convinced by this variable.
Hi Nicolas,
thanks for looking into this.
Nicolas Goaziou n.goaz...@gmail.com writes:
I'm not convinced by this variable. Back-ends are usually so much
different that a global variable aiming at formatting a date timestamp
in any of them doesn't sound very useful.
Though it may be the job
Hi Rasmus,
Rasmus ras...@gmx.us writes:
Would it be desirable if the new exporter took the variable
org-export-date-timestamp-format into consideration when formatting
dates?
I think so. What do you think, Nicolas?
--
Bastien
No answer. But I will share a trick.
Good way to answer such questions is to do this:
M-x find-library RET org-export RET
C-s EXPORT_
and with couple of more C-s es you will end up with something like.
, C-h v org-export-options-alist
| KEYWORD is a string representing a buffer
Hi Nicolas
On Tue, Dec 18, 2012 at 10:21 PM, Nicolas Goaziou n.goaz...@gmail.com wrote:
The problem should now be fixed without using any trick
It is, thank you.
(and no,
`org-export-normalize-links' will not survive the old exporter).
Thanks to your change above I like this cleanup.
François Allisson franc...@allisson.co writes:
Dear org-mode users and developers,
The following concerns Nicolas' new exporter.^
I am totally seduced by the concept of export by subtree, and the
possibility to use properties to set the export options and parameters
(i.e. :EXPORT_TITLE:,
Michael Brand michael.ch.br...@gmail.com writes:
In the meantime I found out that I can simply add
org-export-normalize-links to org-export-before-processing-hook and it
seems to do what I expect. But this is probably not to be included in
Org core because the (hopefully at least only basic)
David Rogers davidandrewrog...@gmail.com writes:
David Rogers davidandrewrog...@gmail.com writes:
My plain-text notes, however, often contain single newlines, which I'd
like to retain. The new ASCII exporter converts them to spaces. If I put
double newlines in the original, then the exporter
Nicolas Goaziou n.goaz...@gmail.com writes:
David Rogers davidandrewrog...@gmail.com writes:
David Rogers davidandrewrog...@gmail.com writes:
My plain-text notes, however, often contain single newlines, which I'd
like to retain. The new ASCII exporter converts them to spaces. If I put
Hello,
David Rogers davidandrewrog...@gmail.com writes:
My plain-text notes, however, often contain single newlines, which I'd
like to retain. The new ASCII exporter converts them to spaces. If I put
double newlines in the original, then the exporter doesn't convert
anything, and leaves them
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
David Rogers davidandrewrog...@gmail.com writes:
My plain-text notes, however, often contain single newlines, which I'd
like to retain. The new ASCII exporter converts them to spaces. If I put
double newlines in the original, then the
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
David Rogers davidandrewrog...@gmail.com writes:
My plain-text notes, however, often contain single newlines, which I'd
like to retain. The new ASCII exporter converts them to spaces. If I put
double newlines in the original, then the
Hello,
Jonathan Leech-Pepin jonathan.leechpe...@gmail.com writes:
The new exporter does not properly parse \n characters in macro definitions.
In the old exporter the following:
#+MACRO: test hello\ngoodbye
{{{test}}}
exports to ASCII as:
hello
goodbye
In the new exporter (e-ascii)
Hi Nicolas
On Wed, Dec 5, 2012 at 10:05 PM, Nicolas Goaziou n.goaz...@gmail.com wrote:
The second one is a more difficult problem. Org Elements usually
translates links on the fly when parsing them: `org-element-link-parser'
calls `org-translate-link'. This function requires
Hello,
Michael Gauland mikely...@no8wireless.co.nz writes:
I've run into trouble using the :wrap option with babel, with the new
exporter.
Using :wrap to put the result in an EXAMPLE block works consistently, but
putting the result into a SRC block is inconsistent. This example:
* :wrap
Hello,
Michael Brand michael.ch.br...@gmail.com writes:
I think the new exporter should still expand link abbreviations also
when in the heading and for all backends. Example with html link on
today’s release_7.9.2-646-g664217:
- Org file:
#+LINK: orgmode http://www.orgmode.org/
* Org
Nicolas Goaziou n.goaziou at gmail.com writes:
I only have time for a cursory look at the problem right now, but
I notice one obvious error: :wrap src fundamental generates wrong Org
syntax. It should be #+END_SRC not #+END_SRC fundamental.
I assume that fixing it on the Babel side should
I would like to hear Nicolas' views before someone gets too excited to
put in a change.
Hi all
I think the new exporter should still expand link abbreviations also
when in the heading and for all backends. Example with html link on
today’s release_7.9.2-646-g664217:
- Org file:
Hi Michael,
Jambunathan K kjambunat...@gmail.com writes:
I would like to hear Nicolas' views before someone gets too excited to
put in a change.
I do agree with Jambunathan.
But let's keep this option in mind anyway.
Best,
--
Bastien
Da: Ista Zahn istaz...@gmail.com
Inviato: Martedì 27 Novembre 2012 15:55
I can't seem to get the new odt exporter working on my Windows machine
at work (it works fine on Linux at home).
[...]
So it seems that the new exporter is not creating content.xml, or
META-INF/manifest.xml. Again this
On Wed, Nov 28, 2012 at 10:15 AM, Giovanni Ridolfi
giovanni.rido...@yahoo.it wrote:
Da: Ista Zahn istaz...@gmail.com
Inviato: Martedì 27 Novembre 2012 15:55
I can't seem to get the new odt exporter working on my Windows machine
at work (it works fine on Linux at home).
[...]
So it seems
Hi!
I am using
Windows 7
Org-mode version 7.9.2 (release_7.9.2-608-g6d01be
GNU Emacs 24.2.1 (i386-mingw-nt6.1.7601) of 2012-08-29 on MARVIN
Libreoffice 3.6.1.2
Exporting works ok for me, contnet.xml is included:
Saving file
Hi, Ista,
Da: Ista Zahn istaz...@gmail.com
Inviato: Lunedì 26 Novembre 2012 23:44
I can't seem to get the new odt exporter working on my Windows machine
at work (it works fine on Linux at home).
[...]
So it seems that the new exporter is not creating content.xml, or
META-INF/manifest.xml.
Hi all,
On Tue, Nov 27, 2012 at 3:40 AM, Giovanni Ridolfi
giovanni.rido...@yahoo.it wrote:
Hi, Ista,
Da: Ista Zahn istaz...@gmail.com
Inviato: Lunedì 26 Novembre 2012 23:44
I can't seem to get the new odt exporter working on my Windows machine
at work (it works fine on Linux at home).
Ista
Your suspicion is confirmed.
If this is true, then either my
understanding of `get-file-buffer' is incorrect or that
`get-file-buffer' is buggy.
Please let me know what I can do to help figure this out.
I have filed a bug:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13013
Jambunathan K kjambunat...@gmail.com writes:
Ista
Your suspicion is confirmed.
If this is true, then either my
understanding of `get-file-buffer' is incorrect or that
`get-file-buffer' is buggy.
Please let me know what I can do to help figure this out.
I have filed a bug:
Thank you, I'm currently working around this with
;; fix f'ed up windows temp directory
(if (eq system-type 'windows-nt)
(setq temporary-file-directory c:/tmp/)
)
in my init.el, and odt export is now working as expected.
Best,
Ista
On Tue, Nov 27, 2012 at 12:46 PM, Jambunathan K
I switched from Windows XP to a Debian few months back. I am not sure
what would make content.xml disappear. Let me investigate...
Meanwhile, check your messages buffer and see whether something looks
suspicious. Following log is from Debian, it tells what the
exporter/Emacs is doing.
Hello,
Jambunathan K kjambunat...@gmail.com writes:
Alan Schmitt alan.schm...@polytechnique.org writes:
I'm trying to remove the postamble in the html-export of a subtree, and
I don't know how to do it. This is what I tried:
C-h v org-e-html-postamble RET
#+BEGIN_SRC org
:PROPERTIES:
Nicolas Goaziou n.goaz...@gmail.com writes:
You can't specify this option at the subtree level, because you can't
specify it with neither a keyword nor an options item.
The property :html-postamble is defined with the following line:
(:html-postamble nil nil org-e-html-postamble)
Its
Alan Schmitt alan.schm...@polytechnique.org writes:
Hello,
I'm trying to remove the postamble in the html-export of a subtree, and
I don't know how to do it. This is what I tried:
C-h v org-e-html-postamble RET
#+BEGIN_SRC org
:PROPERTIES:
:EXPORT_OPTIONS: html-postamble:nil
:END:
Jambunathan K kjambunat...@gmail.com writes:
Alan Schmitt alan.schm...@polytechnique.org writes:
Hello,
I'm trying to remove the postamble in the html-export of a subtree, and
I don't know how to do it. This is what I tried:
C-h v org-e-html-postamble RET
Yes, I had looked there as well
cbe...@tajo.ucsd.edu writes:
When I tried to export a large subtree, it took over *5 minutes* to
export with release_7.9.2-597-gd4b739.
Using the contrib/lisp/*.el files from org-mode-7.8.11
it took *5 seconds*.
The subtree has a couple dozen '...'s in src blocks with ':noweb
yes' and the
Hi Nicolas,
Thanks for your help. I am responding with a couple of points just to
complete this thread, in case someone else is wondering about the same
thing.
Nicolas Goaziou writes:
Myles English mylesengl...@gmail.com writes:
I'd like to use a tikz snippet in a few different documents
Hello,
On 11 November 2012 15:22, Thomas S. Dye t...@tsdye.com wrote:
Aloha all,
The texinfo source for the Org manual has a number of macro definitions
for commands and keys between the end of the header (@finalout) and the
beginning of the Copying section.
The texinfo back-end for the
Aloha Jon,
I'm working on an Org version of the Org manual that (hopefully) can be
used to generate the required texinfo version.
My goal at this point is to export a document that matches org.texi.
My problem is not with the macro definitions, which can be wrapped as
you point out. It is with
Yes, it is ok.
Thanks again,
Fabrice
2012/11/9 Nicolas Goaziou n.goaz...@gmail.com
Hello,
Fabrice Popineau fabrice.popin...@gmail.com writes:
I want to insert a link like :
[[http://foo.org/bar][file:foo.jpg]]
and export it to html. I assume that it should result in a clickable
t...@tsdye.com (Thomas S. Dye) writes:
My goal at this point is to export a document that matches org.texi.
So nice! :-)
I guess I would be much happy myself if I could use Org rather than
Texinfo for some of my own documents. Thanks to all involved! :-)
François
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Eric S Fraga e.fr...@ucl.ac.uk writes:
#+latex_header: \par
Thanks for that. It works fine!
Excellent!
By the way, you may also wish to check out the progressbar beamer theme:
https://github.com/cedricmauclair/beamer-progressbar
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
#+TITLE: export-test.org
#+AUTHOR:Thomas Dye
#+EMAIL: t...@tsdye.com
#+DATE: 2012-11-10 Sat
#+DESCRIPTION: #+KEYWORDS:
#+LANGUAGE: en
#+OPTIONS: H:3 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t :t
#+OPTIONS: TeX:t
Myles English writes:
Hello,
I'd like to use a tikz snippet in a few different documents and it would
be convenient to be able to include it in a latex document like so:
#+CAPTION: a fine figure
#+NAME: figure:fine_figure
#+ATTR_LaTeX: width=5cm
#+BEGIN_LATEX
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
#+EXPORT_SELECT_TAGS: export
#+EXPORT_EXCLUDE_TAGS: noexport
This should be (see `org-export-options-alist'):
#+SELECT_TAGS: export
#+EXCLUDE_TAGS: noexport
Regards,
--
Nicolas Goaziou
Hello,
Myles English mylesengl...@gmail.com writes:
I'd like to use a tikz snippet in a few different documents and it would
be convenient to be able to include it in a latex document like so:
#+CAPTION: a fine figure
#+NAME: figure:fine_figure
#+ATTR_LaTeX: width=5cm
#+BEGIN_LATEX
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
#+EXPORT_SELECT_TAGS: export
#+EXPORT_EXCLUDE_TAGS: noexport
This should be (see `org-export-options-alist'):
#+SELECT_TAGS: export
#+EXCLUDE_TAGS: noexport
Regards,
#+TITLE:
Hi Sebastien,
Sebastien Vauban
wxhgmqzgw...@spammotel.com writes:
Hi Andreas,
Andreas Leha wrote:
how is it possible to add an empty line to a LaTeX header?
Any empty
#+latex_header:
is 'stripped' from the exported document.
Couldn't you use a #+begin/end_LaTeX block instead?
Good
Hi Eric,
Eric S Fraga e.fr...@ucl.ac.uk writes:
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Hi all,
how is it possible to add an empty line to a LaTeX header?
Any empty
#+latex_header:
is 'stripped' from the exported document.
Background:
I am building a beamer
Hello,
Fabrice Popineau fabrice.popin...@gmail.com writes:
I want to insert a link like :
[[http://foo.org/bar][file:foo.jpg]]
and export it to html. I assume that it should result in a clickable image.
Unfortunately, some assertion fails by doing this.
Thank you for reporting this.
I
One problem I am having is that the exported LaTeX replaces the : with
a - to become \ref{tab-niceone} which precludes the use of (e.g.)
\autoref which would need to know that the thing being referenced was a
table by recognising the tab:, no? I am sure there is a good reason
for this, can
Hi Andreas,
Andreas Leha wrote:
how is it possible to add an empty line to a LaTeX header?
Any empty
#+latex_header:
is 'stripped' from the exported document.
Couldn't you use a #+begin/end_LaTeX block instead?
Background:
I am building a beamer presentation using the progress bar from
Nicolas Goaziou writes:
One problem I am having is that the exported LaTeX replaces the : with
a - to become \ref{tab-niceone} which precludes the use of (e.g.)
\autoref which would need to know that the thing being referenced was a
table by recognising the tab:, no? I am sure there is a
Colons are now allowed in targets.
Thanks for submitting the suggestion.
Regards,
--
Nicolas Goaziou
Nicolas Goaziou writes:
Colons are now allowed in targets.
Thanks for submitting the suggestion.
Thanks a lot Nicolas.
In case anyone else finds this useful, here is the filter I'll use to replace
\ref
with \autoref:
(defun my-autoref-filter-link-func (output backend info)
(when
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Hi all,
how is it possible to add an empty line to a LaTeX header?
Any empty
#+latex_header:
is 'stripped' from the exported document.
Background:
I am building a beamer presentation using the progress bar from
Hi Nicolas,
Nicolas Goaziou writes:
Myles English mylesengl...@gmail.com writes:
[..]
So, the label tab:niceone exports as \label{tab-niceone}. Is that right
or am I using the wrong syntax somewhere?
The correct syntax is:
[[tab:niceone]]
It will allow to move back and forth
Hello,
Myles English mylesengl...@gmail.com writes:
If my org file has:
#+CAPTION[Here is a table]: A nice table
#+NAME: tab:niceone
| a |
Look at my \ref{tab:niceone}.
then M-x org-export-dispatch l L gives me:
\begin{table}[htb]
\caption[Here is a table]{\label{tab-niceone}A
On 5 nov. 2012, at 23:18, Nicolas Goaziou n.goaz...@gmail.com wrote:
Hello,
Myles English mylesengl...@gmail.com writes:
If my org file has:
#+CAPTION[Here is a table]: A nice table
#+NAME: tab:niceone
| a |
Look at my \ref{tab:niceone}.
then M-x org-export-dispatch l L
* On Fri 11:22AM, 02 Nov 2012, Hsiu-Khuern Tang (tan...@gmail.com) wrote:
I get
--
1 First level
=
* 1.1 Second level
Something
--
I'd prefer
* Second level
without the 1.1 label, just like with the old
Hello,
Nick Dokos nicholas.do...@hp.com writes:
Michael Gauland mikely...@no8wireless.co.nz wrote:
Nicolas Goaziou n.goaziou at gmail.com writes:
I just tried with a minimal init and it worked. Could you send the
example you're trying to export?
The file is below. With a minimal
Nicolas Goaziou writes:
{{{date(%c)}}} is another macro that is replaced with the #+DATE: value
during export. Since you try to replace #+DATE: value with itself, you
dive into an inf loop.
Which raises the question if this shouldn't be detected and prevented,
at least if direct recursion is
On 30/10/12 20:14, Nicolas Goaziou wrote:
This is {{{time(...)}}}, not {{{date(...)}}}.
{{{date(%c)}}} is another macro that is replaced with the #+DATE: value
during export. Since you try to replace #+DATE: value with itself, you
dive into an inf loop.
I think I understand what's going on
Hello,
Achim Gratz strom...@nexgo.de writes:
Nicolas Goaziou writes:
{{{date(%c)}}} is another macro that is replaced with the #+DATE: value
during export. Since you try to replace #+DATE: value with itself, you
dive into an inf loop.
Which raises the question if this shouldn't be detected
Michael Gauland mikely...@no8wireless.co.nz writes:
I think I understand what's going on now, but I'm still at a loss as to
how to get the date I want. Can I tell the exporter that the date on the
document should be derived from the current time (or the last
modification time), formatted a
Nick Dokos nicholas.do...@hp.com writes:
With a minimal file, I get a cpu pegged at 100% with no end in
sight. Setting debug-on-quit and C-g gives me the following backtrace.
I get this same problem (100% cpu) if I use the date macro in the #+DATE
line; I don't get this if I use the
On 30/10/12 22:29, Nicolas Goaziou wrote:
Doesn't
#+DATE: {{{time(%Y-%m-%d %H:%M)}}}
get you what you expect?
That gives me an empty date string.
signature.asc
Description: OpenPGP digital signature
Michael Gauland mikely...@no8wireless.co.nz wrote:
On 30/10/12 22:29, Nicolas Goaziou wrote:
Doesn't
#+DATE: {{{time(%Y-%m-%d %H:%M)}}}
get you what you expect?
That gives me an empty date string.
Works for me.
Nick
PS Re: the infinite loop with date() - D'oh! That's what I
Hello,
Nick Dokos nicholas.do...@hp.com writes:
Michael Gauland mikely...@no8wireless.co.nz wrote:
On 30/10/12 22:29, Nicolas Goaziou wrote:
Doesn't
#+DATE: {{{time(%Y-%m-%d %H:%M)}}}
get you what you expect?
That gives me an empty date string.
Works for me.
I also get a
Nicolas Goaziou n.goaz...@gmail.com writes:
Michael Gauland mikely...@no8wireless.co.nz writes:
How can I set #+DATE to get an equivalent result?
Doesn't
#+DATE: {{{time(%Y-%m-%d %H:%M)}}}
Works perfectly fine for me. And thanks for the explanation of the
cause of the inf-loop!
The
Eric S Fraga e.fr...@ucl.ac.uk writes:
The problem with the inf-loop now makes sense but the documentation
implies otherwise:
,
| Also,
| `{{{date(FORMAT)}}}' and `{{{modification-time(FORMAT)}}}' refer to
| current date time and to the modification time of the file being
`
I
Nicolas Goaziou n.goaziou at gmail.com writes:
Hello,
Nick Dokos nicholas.dokos at hp.com writes:
Works for me.
I also get a correct date with it, even with a minimal set-up.
Well, this is embarassing. I tackled it fresh, after a cup of coffee (for me)
and a re-start (emacs), and
Nicolas Goaziou n.goaz...@gmail.com writes:
Done. I've also added :repeater-unit for good measure.
Great, thanks!
--
Bastien
Hello,
Michael Gauland mikely...@no8wireless.co.nz writes:
When I provide a format string to the #+DATE: option, the old LaTeX exporter
correctly uses it to format the current date; the new exporter just uses the
format string for the date.
I wasn't aware of that feature. Though, I don't
Nicolas Goaziou n.goaziou at gmail.com writes:
On the other hand, you have a hard-coded macro to solve this problem:
#+DATE: {{{time(%c)}}}
It will work across every back-end (but you need the latest Org version,
since I recently to fixed a bug related to it).
Thanks--that will do
Michael Gauland mikely...@no8wireless.co.nz writes:
Nicolas Goaziou n.goaziou at gmail.com writes:
On the other hand, you have a hard-coded macro to solve this problem:
#+DATE: {{{time(%c)}}}
It will work across every back-end (but you need the latest Org version,
since I recently to
301 - 400 of 588 matches
Mail list logo
