Nicolas Goaziou writes:
> Note that filling/auto-filling will never put you in this situation,
> since Org has a protection mechanism. IOW, if you end up with a list
> marker at the beginning of a line, it's your fault.
I don't use auto-fill in formulas. And yes, I take responsibility for
my faul
Achim Gratz writes:
> Nicolas Goaziou writes:
>> True, that's why there's also inline \[...\]. But you have to accept
>> paragraph limitations (no empty line, do not start a line with list
>> markers...).
>
> Now, given that difference and the fact that these things can span
> over multiple lines
Nicolas Goaziou writes:
> True, that's why there's also inline \[...\]. But you have to accept
> paragraph limitations (no empty line, do not start a line with list
> markers...).
Now, given that difference and the fact that these things can span over
multiple lines and thus include the beginning
Achim Gratz writes:
> There is one remaining difference to a display equation or LaTeX
> fragment: the LaTeX environment will apparently always end the
> paragraph,
Indeed. A LaTeX environment has got the same syntactical value as
a paragraph (both are elements): they cannot be nested.
> someth
Nicolas Goaziou writes:
> I gave you a solution since the beginning of this thread: use a latex
> environment.
After a bit of searching: the answer was in another thread, not in
answer to my original question and I read that answer as "LaTeX blocks
are equivalent to LaTeX environments". I see now
Achim Gratz writes:
>> I gave you a solution since the beginning of this thread: use a latex
>> environment.
>
> It is not a solution because it does not export to HTML.
Of course it does. Try:
--8<---cut here---start->8---
Some latex
\begin{equation*}
2 + 2
Nicolas Goaziou writes:
> I gave you a solution since the beginning of this thread: use a latex
> environment.
It is not a solution because it does not export to HTML. If I need to
write the document mostly in LaTeX I can start with LaTeX and and then
use some LaTeX to HTML translation.
Regards
Achim Gratz writes:
> Nicolas Goaziou writes:
>> The parser parses Org syntax. If you see something else, unless there is
>> an obvious bug, then you are expecting the Org syntax to be different
>> from what it is. It's even the goal of the parser: to define the way to
>> read Org syntax.
>
> Tha
Nicolas Goaziou writes:
> The parser parses Org syntax. If you see something else, unless there is
> an obvious bug, then you are expecting the Org syntax to be different
> from what it is. It's even the goal of the parser: to define the way to
> read Org syntax.
That's what I said. You also defi
Achim Gratz writes:
> Nicolas Goaziou writes:
>> IMO the parser already DTRT. In which case do you think it doesn't?
> DTRT is what you define as DTRT, so yes it does that already. At the
> very least it would be nice if the parser warned when it finds stray
> syntax pieces that are missing thei
Nicolas Goaziou writes:
> IMO the parser already DTRT. In which case do you think it doesn't?
DTRT is what you define as DTRT, so yes it does that already. At the
very least it would be nice if the parser warned when it finds stray
syntax pieces that are missing their match (it took me quite a wh
Bastien writes:
> Hi Achim,
>
> Achim Gratz writes:
>
>> Nicolas Goaziou writes:
It creates this command in the .tex file:
\#+begin$_\mathrm{multicols}$
>>>
>>> It works here. Difficult to say what is wrong in your buffer without
>>> more context.
>>
>> That result looks exactly l
Hi Achim,
Achim Gratz writes:
> Nicolas Goaziou writes:
>>> It creates this command in the .tex file:
>>>
>>> \#+begin$_\mathrm{multicols}$
>>
>> It works here. Difficult to say what is wrong in your buffer without
>> more context.
>
> That result looks exactly like my problem with multiline \[.
Nicolas Goaziou writes:
> henry atting writes:
>
>> Nicolas Goaziou writes:
>>
>>> henry atting writes:
>>>
Here is a minimal example. I use lualatex as tex engine.
#+TITLE: lorem ipsum
#+LANGUAGE: de
#+LaTeX_CLASS: scrartcl
#+LaTeX_CLASS_OPTIONS: [DIV=8,a4paper]
Nicolas Goaziou writes:
>> It creates this command in the .tex file:
>>
>> \#+begin$_\mathrm{multicols}$
>
> It works here. Difficult to say what is wrong in your buffer without
> more context.
That result looks exactly like my problem with multiline \[...\],
i.e. the parser found something it con
Nicolas Goaziou writes:
> henry atting writes:
>
>> Nicolas Goaziou writes:
>>> Try:
>>>
>>> #+attr_latex: :options "{2}"
>>> #+begin_multicols
>>> ...
>>> #+end_multicols
>>
>> It creates this command in the .tex file:
>>
>> \#+begin$_\mathrm{multicols}$
>
> It works here. Difficult to
Nicolas Goaziou writes:
> henry atting writes:
>
>> Here is a minimal example. I use lualatex as tex engine.
>>
>> #+TITLE: lorem ipsum
>> #+LANGUAGE: de
>> #+LaTeX_CLASS: scrartcl
>> #+LaTeX_CLASS_OPTIONS: [DIV=8,a4paper]
>> #+LaTeX_HEADER: \usepackage{fontspec}
>>
>> #+attr_latex: :options "{2
Hi Nicolas,
Nicolas Goaziou writes:
> Hello,
>
> henry atting writes:
>
>> The features are included, does this mean special block should work
>> ``out of the box''? If so something like this
>>
>> #+begin_multicols {2}
>> #+end_multicols
>>
>> should work in LaTeX export (as it did flawlessly
henry atting writes:
> Nicolas Goaziou writes:
>
>> henry atting writes:
>>
>>> Here is a minimal example. I use lualatex as tex engine.
>>>
>>> #+TITLE: lorem ipsum
>>> #+LANGUAGE: de
>>> #+LaTeX_CLASS: scrartcl
>>> #+LaTeX_CLASS_OPTIONS: [DIV=8,a4paper]
>>> #+LaTeX_HEADER: \usepackage{fontspe
henry atting writes:
> Here is a minimal example. I use lualatex as tex engine.
>
> #+TITLE: lorem ipsum
> #+LANGUAGE: de
> #+LaTeX_CLASS: scrartcl
> #+LaTeX_CLASS_OPTIONS: [DIV=8,a4paper]
> #+LaTeX_HEADER: \usepackage{fontspec}
>
> #+attr_latex: :options "{2}"
> #+begin_multicols
>
> * Lorem ip
henry atting writes:
> Nicolas Goaziou writes:
>> Try:
>>
>> #+attr_latex: :options "{2}"
>> #+begin_multicols
>> ...
>> #+end_multicols
>
> It creates this command in the .tex file:
>
> \#+begin$_\mathrm{multicols}$
It works here. Difficult to say what is wrong in your buffer without
m
Hello,
henry atting writes:
> The features are included, does this mean special block should work
> ``out of the box''? If so something like this
>
> #+begin_multicols {2}
> #+end_multicols
>
> should work in LaTeX export (as it did flawlessly with the previous
> exporter); - but it fails.
Try
I'm checking out the new exporter. After some configuration and file
changes it works now, could be worse.
http://article.gmane.org/gmane.emacs.orgmode/65574 says:
> The `org-special-blocks.el' library, which has been moved to “contrib/”,
> is obsolete since its features are included in the new
23 matches
Mail list logo
