Hi,
I'm sorry for my late response.
At Tue, 12 Jun 2012 12:14:29 -0700,
Kyle Machulis wrote:
> :
> But yeah, that is definitely a way to change the output, but on
> further inspection it doesn't look like the right one. If you check
> out calfw-org.el, there's a useful defvar,
> cfw:org-schedule-
Hello,
"Sebastien Vauban"
writes:
> It seems we can't put footnotes in the left part of the
> description. Is it intended? Could that restriction be removed?
That's not really intended, and the fix is easy, but I have a question
first: how would it be rendered in LaTeX?
Apparently,
"\ite
Hi,
just wanted to say it was indeed emacs picking up an ages-old
org-install.el.
Thanks,
Simon
On 06/06/2012 01:46 AM, Nick Dokos wrote:
Simon Thum wrote:
Hi all,
I am using org-mode's taskjuggler export on two machines (win7 standard
emacs 23.3/linux emacs 23.4.2) with 99% identical
On Tue, Jun 12, 2012 at 1:40 AM, Michael Welle wrote:
> The thing Kyle wanted to point out is that you can customise
> the item in the above advice. (message item) just prints the item to the
> status line.
>
> Since I'm a bit short on time at the moment I cheated a little bit and
> manipulated th
On a per file basis, you can add extra lines to your LaTeX export
header by using "#+LATEX_HEADER: ".
(See: http://orgmode.org/org.html#Export-options)
To get your custom commands also to work with the preview of LaTeX
fragments, you may customise the "org-format-latex-header" variable.
Actually
Hi Renato,
renato wrote:
> Hi, I'm really enjoying the org-mode + cdlatex combo. One question
> though, how can I customize the latex header produced by
> org-export-as-latex ? I really need to add some \newcommand and
> \newtheorem statements.
A quick answer. Many, in fact.
Common solutions are
Hi, I'm really enjoying the org-mode + cdlatex combo. One question
though, how can I customize the latex header produced by
org-export-as-latex ? I really need to add some \newcommand and
\newtheorem statements.
best wishes,
renato
Hi Nicolas
On Tue, Jun 12, 2012 at 2:32 PM, Nicolas Goaziou wrote:
> This bug should be fixed now.
I confirm that it is fixed. And as I see from your commit: Thanks to
your modular and therefore stable design it is fixed also for other
cases that I didn't test before with table or list as the on
Hello,
Mark Shoulson writes:
>> ASCII exporter also handle UTF-8. So it's good to have there too.
>
> Really? I would have thought ASCII meant ASCII, as in 7-bit clean
> text.
org-e-ascii.el (as old org-ascii.el) handles ASCII, Latin1 and UTF-8
encodings.
> It looked to me like your solution
Hi Robert and Nicolas,
Robert Yates wrote:
>> I removed this limitation in org-list.el and modified new exporters so
>> they handle checkboxes in description lists correctly (that is by adding
>> checkbox before the tag, not before the description). If it breaks
>> something beyond repair, I'll ju
Hello,
Thorsten Jolitz writes:
> when trying to enhance the HTML back-end of the new exporter with
> interactive HTML elements, one possibility (probably the easiest and
> best) is to write variants for the export functions for some Org
> elements that insert different HTML in the output string
Hello,
Michael Brand writes:
>> [...]
>>
>> - cmd --log-level=wrn -o ::
>> long term + long descr bla bla bla bla
>> bla bla bla bla bla bla bla bla bla bla
>> bla bla bla bla bla bla bla bla bla
>>
>> [...
Hello,
Michael Brand writes:
> Not sure if the following should be supported by
> org-element-interpret-data:
>
> #+BEGIN_SRC org
> ,variable declaration in some programming languages:
> ,- Perl :: the variable declaration can be implicit
> ,- C ::
> , #+BEGIN_SRC C
> ,time_t vari
Michael Welle (2012-06-12 10:40:00 +0200) wrote:
> Ivan Vilata i Balaguer writes:
>
>> Kyle Machulis (2012-06-12 03:47:40 +0200) wrote:
>>
>>> (defadvice qdot/cfw:org-extract-summary (after cfw:org-extract-summary)
>>> "Remove tags and filenames from item summary"
>>> (message item))
>>
>> I
> I removed this limitation in org-list.el and modified new exporters so
> they handle checkboxes in description lists correctly (that is by adding
> checkbox before the tag, not before the description). If it breaks
> something beyond repair, I'll just revert the patch.
This seems to work well fo
Kyle Machulis (2012-06-12 03:47:40 +0200) wrote:
> I used defadvice to fix this:
>
> (defadvice qdot/cfw:org-extract-summary (after cfw:org-extract-summary)
> "Remove tags and filenames from item summary"
> (message item))
>
I placed that and `(ad-activate 'qdot/cfw:org-extract-summary)` in m
16 matches
Mail list logo