On Thursday, 8 Sep 2016 at 17:54, Nick Dokos wrote:
> Can you add a post-processing hook? A simple text replacement might be enough.
This worked very well:
#+begin_src emacs-lisp :exports results :results none
(defun add-wrap-to-textarea (text backend info)
(when (org-export-derived-backen
Am 06.09.2016 um 10:59 schrieb Nicolas Goaziou:
> Hello,
>
> Florian Lindner writes:
>
>> I have this org mode document:
>>
>> #+BEGIN_SRC python :exports results :results file
>> import matplotlib.pyplot as plt, numpy as np
>> x = np.linspace(-2, 2, 1000)
>> plt.plot(x, np.exp(-np.power(4
On 06.09.2016 10:23, Uwe Brauer wrote:
Hello
I would like to modify the auto-fill function such that after every
sentence a new line starts like this
In order to prove our nonlinear instability result, we want to use the
linear growing mode in Proposition to construct small initial data for
t
When I embed LaTeX code in a `#+BEGIN_SRC latex` block and
`org-src-fontify-natively` is set to `t`, the code is fontified as LaTeX
code. But when the code is embedded in a `#+BEGIN_LaTeX` block, there's
no fontification. Is that as intended? Am I missing some setting? Or
could that functionali
On 2016-09-08 11:49, Eric S Fraga wrote:
> To turn wrapping off, I would need to add 'wrap="off"' to the textarea
> form as this option cannot be controlled using CSS unfortunately. I
> don't see any way to do this from org.
Hm. Doesn't the following work?
textarea {
white-space: pre;
}
sig
On Fri, 9 Sep 2016, Kai von Fintel wrote:
When I embed LaTeX code in a `#+BEGIN_SRC latex` block and
`org-src-fontify-natively` is set to `t`, the code is fontified as LaTeX
code. But when the code is embedded in a `#+BEGIN_LaTeX` block, there's no
fontification. Is that as intended? Am I miss
On Friday, 9 Sep 2016 at 15:32, Clément Pit--Claudel wrote:
> On 2016-09-08 11:49, Eric S Fraga wrote:
>> To turn wrapping off, I would need to add 'wrap="off"' to the textarea
>> form as this option cannot be controlled using CSS unfortunately. I
>> don't see any way to do this from org.
>
> Hm.
On Friday, 9 Sep 2016 at 12:06, Kai von Fintel wrote:
> When I embed LaTeX code in a #+BEGIN_SRC latex block and
> org-src-fontify-natively is set to t, the code is fontified as LaTeX
> code. But when the code is embedded in a #+BEGIN_LaTeX block, there's
> no fontification. Is that as intended? A
I am using the org-plus-contrib package in org ELPA.
The export block
#+begin_export latex
...
#+end_export
does not work properly.
It produces
\begin{export}
...
\end{export}
in the .tex file and causes error.
Instead, I still need to use
#+begin_latex
...
s j writes:
> I am using the org-plus-contrib package in org ELPA.
>
> The export block
>
> #+begin_export latex
> ...
> #+end_export
>
> does not work properly.
> It produces
>
> \begin{export}
> ...
> \end{export}
>
> in the .tex file and causes error.
>
> Instead, I still need to use
>
> #+b
Do you mean:
1) Using `call-process' for cases where a single bibliography file is
passed and `process-send-string' when multiple files are used?
2) Using `process-send-string' regardless of the number of bibliography
files? In this case, can we still unify the code between single and
multiple f
Hi,
When one writes latex displayed equations in an org file, is it possible to
achieve the following two points at the same time?
1. In the org buffer, the latex codes have syntax highlighting according to
auctex (auctex installed).
2. The equation can be exported as a displayed equ
Thanks for the clarification!
Jiang
On Sep 9 2016, at 8:41 pm, Nick Dokos wrote:
> s j writes:
>
> > I am using the org-plus-contrib package in org ELPA.
>
> The export block
>
> #+begin_export latex
> ...
> #+end_export
>
> does not work properly.
> It produces
13 matches
Mail list logo
