Aloha Chuck,
"Charles C. Berry" writes:
> On Wed, 22 Apr 2015, Thomas S. Dye wrote:
>
>> Aloha all,
>>
>> Prior to eaa3a761dae, when working in a session, I was able to run this
>> R source code block without problems:
>>
>> ,-
>> | #+header: :file r/adze_
Envoyé de mon iPhone
> Le 23 avr. 2015 à 04:23, Charles C. Berry a écrit :
>
>> On Wed, 22 Apr 2015, Thomas S. Dye wrote:
>>
>> Aloha all,
>>
>> Prior to eaa3a761dae, when working in a session, I was able to run this
>> R source code block without problems:
>>
>> ,--
On Wed, 22 Apr 2015, Thomas S. Dye wrote:
Aloha all,
Prior to eaa3a761dae, when working in a session, I was able to run this
R source code block without problems:
,-
| #+header: :file r/adze_wt_log.pdf
| #+header: :results output graphics
| #+header: :wi
Hello list.
Just tried to export an Org file to ODT but this error appeared (taken
from the Messages buffer):
...
LaTeX to MathML converter not available.
Formatting LaTeX using verbatim
OpenDocument export failed: Assertion failed: (funcall predicate element info)
Tried with a MWE and with a mi
Aloha all,
Prior to eaa3a761dae, when working in a session, I was able to run this
R source code block without problems:
,-
| #+header: :file r/adze_wt_log.pdf
| #+header: :results output graphics
| #+header: :width 4 :height 3
| #+
Nicolas Goaziou wrote:
> Fabrice Niessen writes:
>
>> Could that be stated clearly in the output?
>
> You should ask to whom implemented Worg.
And that is? Bastien?
>> The thing is that I did not touch those links, as you can see in my
>> commit. So, somehow, Org became more strict. And the fact
Fabrice Niessen
writes:
> Could that be stated clearly in the output?
You should ask to whom implemented Worg.
> The thing is that I did not touch those links, as you can see in my
> commit. So, somehow, Org became more strict. And the fact that that file
> wasn't modified for some time means
Hello,
Nicolas Goaziou wrote:
> Fabrice Niessen writes:
>
>> I tried to add a section on Worg (about the ReadTheOrg HTML theme).
>> The Git commit was successfull, the Git push (for which I do have
>> access on Worg) ended with an error code of 0 (hence, successfully?),
>> but it's not visible on
Sebastien Vauban
writes:
> I'd like to enforce org-lint on all my Org docs, either in a find-file
> hook or before export, for example.
>
> Can't you put it in master as well?
No, I can't.
As explained in the original post, "org-lint.el" requires at least Emacs
24.3 (lexical binding, pcase,
Hello,
Fabrice Niessen
writes:
> I tried to add a section on Worg (about the ReadTheOrg HTML theme). The
> Git commit was successfull, the Git push (for which I do have access on
> Worg) ended with an error code of 0 (hence, successfully?), but it's not
> visible on Worg!
The push succeeded,
Here's another update. I added a few more tests.
If there's no more bug report or feedback, I'll simply put it in
a "wip-lint" branch until Org 8.4 starts its development cycle.
Regards,
org-lint.el
Description: application/emacs-lisp
Hello Nicolas,
Nicolas Goaziou wrote:
> Here's another update. I added a few more tests.
>
> If there's no more bug report or feedback, I'll simply put it in
> a "wip-lint" branch until Org 8.4 starts its development cycle.
I'd like to enforce org-lint on all my Org docs, either in a find-file
ho
Hello,
I tried to add a section on Worg (about the ReadTheOrg HTML theme). The
Git commit was successfull, the Git push (for which I do have access on
Worg) ended with an error code of 0 (hence, successfully?), but it's not
visible on Worg!
Any idea why?
--8<---cut here-
Nicolas Goaziou writes:
jorge.alfaro-muri...@yale.edu (Jorge A. Alfaro-Murillo) writes:
Nikolaus Rath writes:
Actually, it seems it does not work for some cases. If I have
a file with
* TODO Item 1 * TODO Item 2 SCHEDULED: <2015-04-24 Fri> *
Heading ** TODO Subitem 1 ** TODO Subitem 1
Hello,
jorge.alfaro-muri...@yale.edu (Jorge A. Alfaro-Murillo) writes:
> Nikolaus Rath writes:
>
>> On Apr 21 2015, Nikolaus Rath wrote:
>>> On Apr 21 2015, jorge.alfaro-muri...@yale.edu (Jorge A.
>>> Alfaro-Murillo) wrote:
Now, if you want to narrow the agenda (C-c a) or org-sparse-tree
Fabrice Niessen writes:
I've just published a new theme, called ReadTheOrg, on
https://github.com/fniessen/org-html-themes.
Thank you very much! I just tried it and it is very nice.
--
Jorge.
Nikolaus Rath writes:
On Apr 21 2015, Nikolaus Rath wrote:
On Apr 21 2015, jorge.alfaro-muri...@yale.edu (Jorge A.
Alfaro-Murillo) wrote:
Now, if you want to narrow the agenda (C-c a) or
org-sparse-tree (C-c /) to show TODO items not SCHEDULED or
DEADLINE'd use the key 'm' and the followi
Nikolaus Rath writes:
Jorge A. Alfaro-Murillo writes:
#+BEGIN_SRC emacs-lisp
(setq org-agenda-prefix-format
'((agenda . " %i %-12:c%?-12t% s")
(timeline . " % s") (todo . " %i %-12:c%-24:b")
(tags . " %i %-12:c") (search . " %i %-12:c")))
(setq org-agend
Hello,
Fabrice Niessen wrote:
> I've just published a new theme, called ReadTheOrg, on
> https://github.com/fniessen/org-html-themes.
>
> It is a clone of the great Sphinx theme used in the
> http://docs.readthedocs.org/en/latest/ site. It gives a beautiful and
> professional style to all your Or
Hi,
David Dynerman writes:
> I've been using links to render text in small caps when exporting to
> LaTeX and HTML, e.g.
>
> [[latex:textsc][this is in small caps]]
>
> This worked fine in 8.2.10, but causes an error in latest. When I try to
> export the file to LaTeX, the export fails with:
>
>
If you don't mind to live with part-chapter-section instead
chapter-section-subsection:
---8<-orgmode src>8---
#+LaTeX_CLASS: book
#+LaTeX_HEADER: \let\part\chapter
#+LaTeX_HEADER: \let\chapter\section
#+LaTeX_HEADER: \let\section\subsection
---8<---
21 matches
Mail list logo
