Hello,
Neil Smithline writes:
> I've looked at org-element.el and don't really see how it will make writing
> other Org Mode to HTML converter easier. org-element.el is, well it's
> elisp. Very elispy. No surprise but I'm not sure that it can easily be
> converted to another language.
>
> Is Nic
Bastien writes:
> 1. There is already a new Org>HTML exporter, written by Jambunathan.
>Try adding contrib/lisp/ to your load path, then
>
>(require 'org-export)
>(require 'org-e-html)
>
>then M-x org-export-dispatch RET h
>
>See the result.
There are a bunch of org-e-html-*
Hi Mark,
"Mark E. Shoulson" writes:
> It's a very tiny patch, but one that probably should have happened
> before.
Yes. Surprised nobody reported this already.
I applied the patch, but I had to add a ChangeLog myself. Please
provide it next time.
Thanks!
--
Bastien
Hi François,
François Pinard writes:
> There is some machinery on my side involved into publication, which I
> would rather avoid if not necessary. My little problem is that Org
> checks the file time stamp, and Emacs does not distinguish, of course,
> if I modify a part which is within a :noex
Hi Nicolas,
Nicolas Goaziou writes:
>>> Further, with orgstuct++-mode, trying to add a new line (i.e. my
>>> response), I get the following error message:
>>>
>>> ,
>>> | org-indent-line-function: Lisp nesting exceeds `max-lisp-eval-depth' [3
>>> times]
>>> `
>
> I confirm the problem w
Hi Charles,
cbe...@tajo.ucsd.edu writes:
> It fills normal text, but leaves src blocks alone.
>
> Maybe add something to one of the org-mode hooks ?
`org-auto-fill-function' already exists in the code, adding
a new function with the same name would confuse things.
I patched the current `org-a
Hi Benjamin,
Benjamin Motz writes:
> invoking fill-paragraph on the following org-code will delete the
> newline after \end{equation}:
>
> The relation
> \begin{equation}
> E=mc^2
> \end{equation}
> won't be further discussed here.
>
> This behaviour is undesirable because it makes the org-text
Hi George,
George Kettleborough writes:
> On Sun, Apr 29 2012, Bastien wrote:
>> `global-mode-string' and ̀frame-title-format' are list by default
>> and they cannot be customized. They can be manually set to a string,
>> but that's a mistake (okay, `global-mode-string' is a misleading name.)
>
Hello,
Bastien writes:
> I pushed a fix -- can you test and confirm?
I get the following error every time I try to indent:
"org-between-regexps-p: Variable binding depth exceeds max-specpdl-size"
Regards,
--
Nicolas Goaziou
Bastien writes:
> Hi François,
Bonjour chez vous! :-)
> François Pinard writes:
>> There is some machinery on my side involved into publication, which I
>> would rather avoid if not necessary.
> Please don't hesitate to share it you think other people could find it
> useful.
Probably not ge
Hello,
Bastien writes:
> Benjamin Motz writes:
>
>> invoking fill-paragraph on the following org-code will delete the
>> newline after \end{equation}:
>>
>> The relation
>> \begin{equation}
>> E=mc^2
>> \end{equation}
>> won't be further discussed here.
>>
>> This behaviour is undesirable becau
Hi Nicolas,
Nicolas Goaziou writes:
>> I pushed a fix -- can you test and confirm?
>
> I get the following error every time I try to indent:
In org-mode or in message-mode?
> "org-between-regexps-p: Variable binding depth exceeds
> max-specpdl-size"
Does (setq max-specpdl-size 1) help
Nicolas Goaziou writes:
> Bastien writes:
>
>> I pushed a fix -- can you test and confirm?
>
> I get the following error every time I try to indent:
>
> "org-between-regexps-p: Variable binding depth exceeds
> max-specpdl-size"
If you are in message-mode, please also provide the value of
`o
Bastien writes:
> Nicolas Goaziou writes:
>> I get the following error every time I try to indent:
>
> In org-mode or in message-mode?
I meant in Message mode.
>> "org-between-regexps-p: Variable binding depth exceeds
>> max-specpdl-size"
>
> Does (setq max-specpdl-size 1) help in any
Bastien writes:
> Nicolas Goaziou writes:
>
>> Bastien writes:
>>
>>> I pushed a fix -- can you test and confirm?
>>
>> I get the following error every time I try to indent:
>>
>> "org-between-regexps-p: Variable binding depth exceeds
>> max-specpdl-size"
>
> If you are in message-mode, pl
* lisp/org-footnote.el (org-footnote-new): Don't call
org-footnote-unique-label if org-footnote-auto-label is set to
random.
Calling org-footnote-unique-label calls org-footnote-all-labels, which
can dramatically slow down footnote creation in a buffer with many
footnotes. This is unecessary
Aloha all,
I've been tinkering with Karl Voit's ACM-SIG export project and have
almost met the project goal using the old exporter. The old LaTeX
exporter is able to produce a file that is close to the example provided
by ACM and which LaTeX is able to compile without error. (The main
problem is
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> I'm starting now to work out the port to the new exporter. I first
> tried the new LaTeX exporter, which stops with this error:
> Symbol's value as variable is void: value
It should be fixed in master.
> The new html exporter exports the file wit
Aloha Nicolas,
Nicolas Goaziou writes:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> I'm starting now to work out the port to the new exporter. I first
>> tried the new LaTeX exporter, which stops with this error:
>> Symbol's value as variable is void: value
>
> It should be fixed in
Hi there!
I have these custom agendas in my org-agenda-custom-commands variable:
("w" . "Work Related")
("w1" "Test ok report"
((agenda "" (
(org-agenda-clockreport-mode t)
("w2"
Hi Sébastien,
"Sebastien Vauban"
writes:
> Let's come back to time values:
>
> @2$2=1:23;t
>
> means, for me, that:
>
> - the value 1:23 should be assigned to the cell
> - that value should be formatted as a fraction.
>
> Hence, I'd expect to see `1.38' (and not `0:00').
This works correctl
Aloha,
The new LaTeX exporter doesn't properly handle source code blocks with
:exports results. The following snippet exports correctly with the old
exporter.
Org-mode source
#+name: ACM-categories
#+header: :var c=categories
#+header: :results latex
#+header: :exports results
#+BEGI
t...@tsdye.com (Thomas S. Dye) writes:
> The new LaTeX exporter doesn't properly handle source code blocks with
> :exports results. The following snippet exports correctly with the old
> exporter.
>
> Org-mode source
> #+name: ACM-categories
> #+header: :var c=categories
> #+header: :r
Nicolas Goaziou writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> The new LaTeX exporter doesn't properly handle source code blocks with
>> :exports results. The following snippet exports correctly with the old
>> exporter.
>>
>> Org-mode source
>> #+name: ACM-categories
>> #+head
t...@tsdye.com (Thomas S. Dye) writes:
> Here is a problem with CAPTION and ATTR_LaTeX lines. Note that the
> \table{} environment wasn't established.
>
> Org-mode
> #+CAPTION: Frequency of Special Characters
> #+ATTR_LaTeX: align=|c|c|l|
>
> |-+-+---
Bastien writes:
> Does #+INCLUDE: suits your needs?
Oh! I never used a colon after #+INCLUDE. Checking the Org manual, the
colon is systematically there, except within the last paragraph of node
/Updating files/. Maybe it could be added for consistency?
I did not notice my error as everythin
Hi François,
François Pinard writes:
> Bastien writes:
>
>> Does #+INCLUDE: suits your needs?
>
> Oh! I never used a colon after #+INCLUDE. Checking the Org manual, the
> colon is systematically there, except within the last paragraph of node
> /Updating files/. Maybe it could be added for c
Nicolas Goaziou writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Here is a problem with CAPTION and ATTR_LaTeX lines. Note that the
>> \table{} environment wasn't established.
>>
>> Org-mode
>> #+CAPTION: Frequency of Special Characters
>> #+ATTR_LaTeX: align=|c|c|l|
>>
>> |--
François Pinard writes:
> Our dear Bastien writes:
>> We could have a #+PUBLISH: option allowing to tell whether a file
>> should be published or not. If we had this, we could then check
>> whether a section without the :noexport: tag has been modified...
>> and dynamically set the buffer publi
The manual says, in section 4.2 Internal links:
Targets may be located anywhere; sometimes it is convenient to put
them into a comment line. For example
# <>
But if I use such commented targets, then the new exporter does not see
them, neither the one to LaTeX nor the HTML one.
Hello,
Rafael writes:
> The manual says, in section 4.2 Internal links:
>
> Targets may be located anywhere; sometimes it is convenient to put
> them into a comment line. For example
>
> # <>
>
> But if I use such commented targets, then the new exporter does not see
> them, nei
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> I can't get a \begin{figure*} environment with multicolumn.
>
> Org-mode
> #+CAPTION: A sample black and white graphic (.eps format) that needs to span
> two columns of text.
> #+ATTR_LaTeX: multicolumn
> [[file:flies.eps]]
>
32 matches
Mail list logo
