Hi Nicolas,
Nicolas Goaziou wrote:
t...@tsdye.com (Thomas S. Dye) writes:
I defined a new entity in org-entities-user, but the new exporter
appears to ignore it. Does it look at this variable, or just
org-entities?
I used:
(add-to-list 'org-entities-user '(omacr \\={o} nil #333; o o ō))
Hi Nicolas,
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
I defined a new entity in org-entities-user, but the new exporter
appears to ignore it. Does it look at this variable, or just
org-entities?
I used:
(add-to-list 'org-entities-user
Sebastien Vauban
wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org writes:
Nicolas Goaziou wrote:
I used:
(add-to-list 'org-entities-user '(omacr \\={o} nil #333; o o ō))
without a problem.
IIUC, you specify how to translate some LaTeX-like command to the different
back-ends. But I
Nicolas Goaziou n.goaz...@gmail.com writes:
IIUC, you specify how to translate some LaTeX-like command to the different
back-ends. But I don't see DocBook nor OOo in the list:
┏
┃ User-defined entities used in Org-mode to produce special characters.
┃ Each entry in this list
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
This docstring at line 186 of org-e-latex.el is incomplete
Fixed.
BTW, I have the experimental LaTeX exporter working on a real project
now. It is performing very well for me.
Good to hear. I still need to fix the #+toc: listings keyword
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
This docstring at line 186 of org-e-latex.el is incomplete
Fixed.
BTW, I have the experimental LaTeX exporter working on a real project
now. It is performing very well for me.
Good to hear. I
t...@tsdye.com (Thomas S. Dye) writes:
The old exporter recognized LaTeX commands for accented characters. So,
\=o in the Org mode file would yield \={o} in the LaTeX file. The new
exporter gives $\backslash$=o for this construct.
Indeed, the parser recognizes LaTeX commands and
Nicolas Goaziou n.goaz...@gmail.com writes:
t...@tsdye.com (Thomas S. Dye) writes:
The old exporter recognized LaTeX commands for accented characters. So,
\=o in the Org mode file would yield \={o} in the LaTeX file. The new
exporter gives $\backslash$=o for this construct.
Indeed, the
Hi Nicolas,
I couldn't make this work.
Nicolas Goaziou n.goaz...@gmail.com writes:
t...@tsdye.com (Thomas S. Dye) writes:
The old exporter recognized LaTeX commands for accented characters. So,
\=o in the Org mode file would yield \={o} in the LaTeX file. The new
exporter gives
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
I defined a new entity in org-entities-user, but the new exporter
appears to ignore it. Does it look at this variable, or just
org-entities?
I used:
--8---cut here---start-8---
(add-to-list 'org-entities-user
t...@tsdye.com (Thomas S. Dye) writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
There are three states for creator, on, off and comment, and two places
to insert the information (in hypersetup and at the end of the exported
data).
What would be a correct way to handle the different
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
References to org-e-latex-packages-alist in org-e-latex.el docstrings
should be to org-export-latex-packages-alist.
This should be fixed (along with your other report). Thanks for both
reports.
Regards,
--
Nicolas Goaziou
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
I've commited an ASCII back-end for new export engine.
Assuming contrib directory is in your load-path, you just need to
(require 'org-export) to have both LaTeX and ASCII exporters ready to
boot.
You can then access to the dispatcher
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
I haven't been able to export a listing yet. The following source
exports with the old exporter, but fails with the experimental
exporter.
This long standing bug should be fixed now.
Regards,
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
I've commited an ASCII back-end for new export engine.
Assuming contrib directory is in your load-path, you just need to
(require 'org-export) to have both LaTeX and ASCII exporters ready to
boot.
You can then access to the dispatcher
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
I've commited an ASCII back-end for new export engine.
Assuming contrib directory is in your load-path, you just need to
(require 'org-export) to have both LaTeX and ASCII exporters ready to
boot.
You can then access to the dispatcher
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
I haven't been able to export a listing yet. The following source
exports with the old exporter, but fails with the experimental
exporter.
This long standing bug should be fixed now.
Regards,
--
Nicolas Goaziou
Nicolas Goaziou n.goaz...@gmail.com writes:
No. Headlines, along with items, keywords and sections, can't have
affiliated keywords. Though, they have properties. It may be done with:
:PROPERTIES:
:NUMBERING: nil
:END:
But it's still new syntax. It could also be narrowed
to
Nicolas Goaziou n.goaz...@gmail.com writes:
I may be bold, but I still don't get it. num:something is a global
option. We're talking about specifying _individually_ which headline
wouldn't be numbered. How would a global option solve a local problem?
Had another thought about it: if the
Hi N,
Some comments on your great work:
Recent version errors with wrong type argument, but I can't
privacy-wash yet to show the whole stack trace.
make-string(-1 32)
(concat aligned-cell (make-string (- col-width ...) 32))
(format %s (concat aligned-cell (make-string ... 32)))
(let*
Hello,
Samuel Wales samolog...@gmail.com writes:
Recent version errors with wrong type argument, but I can't
privacy-wash yet to show the whole stack trace.
I don't need the whole stack trace, but there is at least one table in
your buffer that causes problems to the exporter. I'd need to see
On 2012-01-28, Nicolas Goaziou n.goaz...@gmail.com wrote:
If you don't know which one it is, you can successively mark each table
in that buffer and use org-export-dispatch with the region active (it
will only export the region) until the culprit is found.
I get Before first headline at
Samuel Wales samolog...@gmail.com writes:
On 2012-01-28, Nicolas Goaziou n.goaz...@gmail.com wrote:
If you don't know which one it is, you can successively mark each table
in that buffer and use org-export-dispatch with the region active (it
will only export the region) until the culprit is
On 2012-01-28, Nicolas Goaziou n.goaz...@gmail.com wrote:
- This is an item with some text.
Sets off much less.
No, I mean that this is a useful way to send things to people who use
proportional fonts.
But in the simplest cases, tables will look ugly with proportional
fonts, no matter if
Samuel Wales samolog...@gmail.com writes:
On 2012-01-28, Nicolas Goaziou n.goaz...@gmail.com wrote:
- This is an item with some text.
Sets off much less.
Well. I'm still not sure why plain lists should have their own
indentation. In that case, tables, latex-environments, etc. should too.
I have no objection to implement limited numbering in both LaTeX and
ASCII back-ends, but I'd like to know if it can be handled consistently
in every other major back-end, too. I'm CC-ing Jambunathan to know his
opinion about it.
I can support this in ODT exporter. We can make this a feature
Hello,
Achim Gratz strom...@nexgo.de writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
But it's still new syntax. It could also be narrowed
to :LATEX_NUMBERING: nil, but I think that this feature, if implemented,
should be available for every major back-end, much like num:1.
Unless I
On Fri, Jan 27, 2012 at 01:58:26PM +0100, Nicolas Goaziou wrote:
Achim Gratz strom...@nexgo.de writes:
Unless I miss something, if num:* would be allowed in addition to
integers, the LaTeX crowd would be pleased, no terribly new syntax would
be needed and all other backends could take note
Hello,
Rick Frankel r...@rickster.com writes:
On Fri, Jan 27, 2012 at 01:58:26PM +0100, Nicolas Goaziou wrote:
Achim Gratz strom...@nexgo.de writes:
Unless I miss something, if num:* would be allowed in addition to
integers, the LaTeX crowd would be pleased, no terribly new syntax would
Hello,
Jambunathan K kjambunat...@gmail.com writes:
I have no objection to implement limited numbering in both LaTeX and
ASCII back-ends, but I'd like to know if it can be handled consistently
in every other major back-end, too. I'm CC-ing Jambunathan to know his
opinion about it.
I can
Hi all,
Nicolas Goaziou n.goaz...@gmail.com writes:
I tend to agree here. This can be obviously discussed on the list,
detail specifications and so on, but I'd rather postpone any real coding
in this area until new exporter is installed in core.
I strongly support this. We should try to
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
Jambunathan K kjambunat...@gmail.com writes:
I have no objection to implement limited numbering in both LaTeX and
ASCII back-ends, but I'd like to know if it can be handled consistently
in every other major back-end, too. I'm CC-ing
Nicolas Goaziou n.goaz...@gmail.com writes:
I may be bold, but I still don't get it. num:something is a global
option. We're talking about specifying _individually_ which headline
wouldn't be numbered. How would a global option solve a local problem?
It doesn't, I missed that point. I don't
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
I've commited an ASCII back-end for new export engine.
Assuming contrib directory is in your load-path, you just need to
(require 'org-export) to have both LaTeX and ASCII exporters ready to
boot.
You can then access to the dispatcher
Nicolas Goaziou n.goaz...@gmail.com writes:
A way to set individual headings as numbered or unnumbered would be
deluxe. Perhaps this is possible, but I haven't found it?
It would require to modify Org's syntax (how to tell which headline has
to be numbered and which has not?). It is not
Jambunathan K kjambunat...@gmail.com writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
A way to set individual headings as numbered or unnumbered would be
deluxe. Perhaps this is possible, but I haven't found it?
It would require to modify Org's syntax (how to tell which headline has
to
Tom
The aspect I am exploring is this:
Does numbering behavious occur uniformly for a *given* level? For
example, are we talking of a scenario where level 3 heading in Tree-1 is
numbered while level 3 heading on a Tree-2 is unnumbered. What would be
the behaviour of level 4 heading in Tree-1.
Jambunathan K kjambunat...@gmail.com writes:
Does numbering behavious occur uniformly for a *given* level? For
example, are we talking of a scenario where level 3 heading in Tree-1 is
numbered while level 3 heading on a Tree-2 is unnumbered. What would be
the behaviour of level 4 heading in
Sent from my iPhone
On Jan 27, 2012, at 9:21 AM, Achim Gratz strom...@nexgo.de wrote:
Jambunathan K kjambunat...@gmail.com writes:
Does numbering behavious occur uniformly for a *given* level? For
example, are we talking of a scenario where level 3 heading in Tree-1 is
numbered while level
Thomas S. Dye t...@tsdye.com wrote:
\paragraph and \subparagraph can both be numbered sections in LaTeX.
The names are confusing. Apparently, the alternatives,
\subsubsubsection and \subsubsubsubsection weren't appealing.
No wonder - it's sorta like writing Avogadro's number like this:
Sent from my iPhone
On Jan 27, 2012, at 8:31 AM, Jambunathan K kjambunat...@gmail.com wrote:
Tom
The aspect I am exploring is this:
Does numbering behavious occur uniformly for a *given* level? For
example, are we talking of a scenario where level 3 heading in Tree-1 is
numbered
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
I think that your understanding of the new exporter architecture is
intimate and secure. I'm happy to follow your lead here.
I know for sure my way around the new exporter, but my LaTeX skills
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
I think that your understanding of the new exporter architecture is
intimate and secure. I'm happy to follow your lead here.
I know for sure my way around the new exporter, but my LaTeX skills
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
You mentioned unnumbered headlines. I wonder, would it be possible (or
useful) to have the num: option take an integer (like toc:)? As I
understand it now, its value is either nil or not nil. It doesn't
manipulate \secnumdepth, but instead
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
You mentioned unnumbered headlines. I wonder, would it be possible (or
useful) to have the num: option take an integer (like toc:)? As I
understand it now, its value is either nil or not nil. It
t...@tsdye.com (Thomas S. Dye) writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
t...@tsdye.com (Thomas S. Dye) writes:
A way to set individual headings as numbered or unnumbered would be
deluxe. Perhaps this is possible, but I haven't found it?
It would require to modify Org's syntax
Nicolas Goaziou n.goaz...@gmail.com writes:
But it's still new syntax. It could also be narrowed
to :LATEX_NUMBERING: nil, but I think that this feature, if implemented,
should be available for every major back-end, much like num:1.
Unless I miss something, if num:* would be allowed in
Nicolas Goaziou n.goaz...@gmail.com writes:
t...@tsdye.com (Thomas S. Dye) writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
t...@tsdye.com (Thomas S. Dye) writes:
A way to set individual headings as numbered or unnumbered would be
deluxe. Perhaps this is possible, but I haven't found
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
I think that your understanding of the new exporter architecture is
intimate and secure. I'm happy to follow your lead here.
I know for sure my way around the new exporter, but my LaTeX skills
aren't on par with that knowledge.
Anyway, I've
Nicolas Goaziou n.goaz...@gmail.com writes:
[...]
As a side note, #+label has been deprecated in favor of #+name (though
the former is immediately translated into the latter at parse time).
Sorry for hijacking this thread. But this side note is only valid for
the new exporter, correct? As
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
#+CAPTION[An example photograph]: An example photograph.
#+NAME: fig:photo
for me, yields:
\caption{\label{fig:photo}An example photograph}
I was expecting:
\caption[An example
t...@tsdye.com (Thomas S. Dye) writes:
The file name passed to \includegraphics is formed like this:
~/path/to/graphics/file
My LaTeX doesn't recognize this as a path.
The old exporter passed a file name where the tilde was expanded:
/Users/user/path/to/graphics/file
It should be fixed
2) If the source block is executed in buffer with (org-ctrl-c-ctrl-c),
as shown above, then the exporter appears to export the in-buffer
results /and/ the export-generated results (where :exports is results
or both) resulting in two sets of identical results in the export.
It's out of
Hello,
Eric Schulte eric.schu...@gmx.com writes:
It's out of exporter's scope.
I disagree. The current exporter conforms to the value of the :results
header argument (e.g., silent, replace, append, etc...) when executing
code blocks during export. I see no reason why the new exporter
Nicolas Goaziou n.goaz...@gmail.com writes:
t...@tsdye.com (Thomas S. Dye) writes:
The file name passed to \includegraphics is formed like this:
~/path/to/graphics/file
My LaTeX doesn't recognize this as a path.
The old exporter passed a file name where the tilde was expanded:
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
A quick question and a couple of comments on the LaTeX exporter.
With the old exporter I set (setq org-export-latex-hyperref-format
\\ref{%s}) so a link to a headline would cross reference properly
Hello,
Samuel Wales samolog...@gmail.com writes:
In 22, latest git:
downcase: Args out of range: image-keep-calm, 651500, 651505
match-string(1 image-keep-calm)
(downcase (match-string 1 val))
(concat :macro- (downcase (match-string 1 val)))
(intern (concat :macro- (downcase
Hi Nicolas
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
I've commited an ASCII back-end for new export engine.
Assuming contrib directory is in your load-path, you just need to
(require 'org-export) to have both LaTeX and ASCII exporters ready to
boot.
You can then access to the
Hello,
Martyn Jago martyn.j...@btinternet.com writes:
I've been playing with (org-export-dispatch) with regard to some simple
source blocks and have a couple of observations (apologies in advance if
source blocks are not fully implemented yet).
The test code is:
* Test
#+begin_src
On 2012-01-22, Nicolas Goaziou n.goaz...@gmail.com wrote:
Hello,
Also, judging by the backtrace, it seems that you are using a strange
syntax for defining macros. Would you mind telling me what your
#+macro: line is like, and what you do expect from it?
I always export a subtree and not a
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
I've commited an ASCII back-end for new export engine.
Assuming contrib directory is in your load-path, you just need to
(require 'org-export) to have both LaTeX and ASCII exporters ready to
boot.
You can then access to the dispatcher
t...@tsdye.com (Thomas S. Dye) writes:
I think there might be a problem with the regular expression for
captions on line 703 or org-e-latex.el. I have a dim understanding of
regular expressions and the various parsers, but I suspect the problem
is in this part: [^][].
At any rate, this
Aloha Nicolas,
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
A quick question and a couple of comments on the LaTeX exporter.
With the old exporter I set (setq org-export-latex-hyperref-format
\\ref{%s}) so a link to a headline would cross
Aloha Nicolas,
Nicolas Goaziou n.goaz...@gmail.com writes:
t...@tsdye.com (Thomas S. Dye) writes:
I think there might be a problem with the regular expression for
captions on line 703 or org-e-latex.el. I have a dim understanding of
regular expressions and the various parsers, but I
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
#+CAPTION[An example photograph]: An example photograph.
#+NAME: fig:photo
for me, yields:
\caption{\label{fig:photo}An example photograph}
I was expecting:
\caption[An example photograph]{\label{fig:photo}An example
photograph}
I get the
Hello,
I've commited an ASCII back-end for new export engine.
Assuming contrib directory is in your load-path, you just need to
(require 'org-export) to have both LaTeX and ASCII exporters ready to
boot.
You can then access to the dispatcher with M-x org-export-dispatch and
test various
Hi Nicolas,
On 2012-01-21, Nicolas Goaziou n.goaz...@gmail.com wrote:
You can then access to the dispatcher with M-x org-export-dispatch and
test various configurations from there.
There is a problem with the dispatcher that prevents me from testing.
It exceeds 78 columns, but more
Two feature requests:
1) optionally squeeze blank lines
2) optionally unfill paragraphs
--
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
===
Bigotry against people with serious diseases is still bigotry.
Hello,
Samuel Wales samolog...@gmail.com writes:
There is a problem with the dispatcher that prevents me from testing.
It exceeds 78 columns,
[...]
No. The standard UI doesn't even exceed 60 columns. You must be using
something else.
I can't tell if c-c c-e A is yours or the old one.
In 22, latest git:
downcase: Args out of range: image-keep-calm, 651500, 651505
match-string(1 image-keep-calm)
(downcase (match-string 1 val))
(concat :macro- (downcase (match-string 1 val)))
(intern (concat :macro- (downcase ...)))
(plist-put nil (intern (concat :macro- ...))
70 matches
Mail list logo
