Hi all,
I am having problems with the export of a minimal org file:
,
| #+PROPERTY: session *R*
|
| * Test
|
| | dtrn | xgnd |
| |--+---|
| | engd | src_R[:exports results :results raw rep
Also interested in if this is possible and what do you use to highlight
LaTeX code blocks.
On Wed, Jul 4, 2012 at 9:11 AM, Ilya Shlyakhter wrote:
> dear org-moders,
> is it possible to syntax-highlight inline LaTeX fragments,
> such as $V$ or \cite{smith2012generating} ?
> I know you can highligh
Thanks, that fixed it but another question.
if you export the whole file then and not just the selection can you use a
tag or property to specify a different directory to export into instead of
the same directory as the org file. Will creating the Property Tag at the
top level work for this??
Als
In agenda log mode, the org-agenda-done face is excellent. However,
todo keywords and priorities are still faceified specially like they
are in the agenda.
Perhaps org-agenda-done face should be applied later, so that the
entire line is green by default.
I get distracted by the repeat-to todo ke
Hello Nicolas,
On Mon, Jul 2, 2012 at 2:22 PM, Nicolas Goaziou wrote:
>
> This should be possible with `org-e-beamer-environments-extra', i.e.
>
> (add-to-list 'org-e-beamer-environments-extra
>'("onlyenv" "O" "\\begin{onlyenv}%a" "\\end{onlyenv}"))
>
> Then you set headline's B
On 7/3/12, Samuel Wales wrote:
> My need for undo-boundary to work the way it did
That should read, "My need for self-insert-command to work
the way it did".
On 7/3/12, Stefan Monnier wrote:
>> self-insert-command. Even just turning that magic 20 number into a
>> variable would help.
>
> Providing it as a variable would be very easy, indeed.
Hi Stefan,
To clarify, that is actually the only thing that I need as a user for
self-insert-command. It wou
dear org-moders,
is it possible to syntax-highlight inline LaTeX fragments,
such as $V$ or \cite{smith2012generating} ?
I know you can highlight LaTeX code blocks, but I'm looking specifically
for highlighting of inline fragments.
thanks for help,
ilya
> The first is that it hardcodes the clustering by 20.
I guess that's the problem which is not new.
> This was possible to work around before Emacs 24. You could advise
> self-insert-command or wrap it. This is why Org was able to control
> this with a variable to support clustering or not clus
I'm trying to export a table with the following cell:
BAT_30_CCR01_OUV_ZONE_PCE_30_2A_102_&_30_2A_101
The ampersand seems to be messing everything... I obtain this when I export:
BAT\_{}30\_{}CCR01\_{}OUV\_{}ZONE\_{}PCE\_{}30\_{}2A\_{}102_\&_30\_{}2A\_{}101
For this to export normally, I would
On 25.06.2012 13:35, Toby Cubitt wrote:
> On Sun, Jun 24, 2012 at 11:52:41PM +0200, Toby Cubitt wrote:
>> On Sun, Jun 24, 2012 at 11:39:08PM +0200, Bastien wrote:
>>> Hi Toby,
>>>
>>> Toby Cubitt writes:
>>>
For some unknown reason, org-mode is causing the undo boundary between
the (2 .
On 7/3/12, Stefan Monnier wrote:
> Indeed, self-insert-command used to be treated specially by the
> read-eval-loop and the merging was performed there. Now this command is
> handled like any other, and self-insert-command does the merging itself.
> In most cases the result is the same, but the b
> Which is what one wants. Someone seems to be merging the self-insert
> commands in your situation. Probably the native merging code has
> changed in recent Emacs itself.
Indeed, self-insert-command used to be treated specially by the
read-eval-loop and the merging was performed there. Now thi
Dear all,
let say I have these lines:
#+PROPERTY: session *py*
#+PROPERTY: results output
#+BEGIN_SRC python
import matplotlib.pyplot as plt
a=[1,2,3]
#+END_SRC
I execute the code block, no problem
Then I execute this:
#+BEGIN_SRC python
plt.plot(a)
#+END_SRC
boom, emacs hangs
result doesn't c
On Mon, Jul 02, 2012 at 08:51:48AM +0200, Martin Pohlack wrote:
> > I'm still not entirely convinced that the boundary discarding logic in
> > org-self-insert-command is correct. For example, if I do the following:
> >
> > 1. Type some text at some location in an org-mode buffer
> > 2. Move to ano
On 03.07.2012 11:57, Toby Cubitt wrote:
> On Mon, Jul 02, 2012 at 08:51:48AM +0200, Martin Pohlack wrote:
>>> I'm still not entirely convinced that the boundary discarding logic in
>>> org-self-insert-command is correct. For example, if I do the following:
>>>
>>> 1. Type some text at some location
Thank you, Tom.
It works like a charm!
Now, I will read the document one more time very carefully and throughly.
James
On Mon, Jul 2, 2012 at 7:25 PM, Thomas S. Dye wrote:
> James Kang writes:
>
> > Hi,
> >
> > I have been using code blocks with the following way to pass one's
> > output to
Just a heads-up: I just pulled, regenerated autoloads
(release_7.8.11-107-ga69f4b8),
and ran ``make check''. I got
,
| ...
| Ran 193 tests, 192 results as expected, 1 unexpected (2012-07-03
10:57:01-0400)
| 6 expected failures
|
| 1 unexpected results:
|FAILED test-ob-lob/call-with-he
Hi all,
I am having trouble to find a way to set a short title for the exported
beamer document.
Illustration:
I'd like to see
,
| \title[short title]{long title}
`
in the exported latex document.
The first shot
,
| #+TITLE: [short title]{long title}
`
was too easy, I guess.
Hi,
If I have something like
,---
| #+name: dot-code
| #+begin_src perl :results output :cache no
| print < "Node\\nA"
| Core -> "Node\\nB"
| }
| END
|
| #+end_src
|
| #+header: :var input=dot-code
| #+header: :file tmp.pdf
| #+header: :cmdline -Kneato -T
Hello,
Luis Anaya writes:
> In terms of keywords, they all have to be revised, and many of them
> are going to be removed. (Like long tables). I'll changed them from
> tag=value to :blah value, right now they're not really meaningful for
> groff and many of them stubbed.
Ok.
> I proposed to k
Hello,
Jeffrey Spencer writes:
> When I input subtree options for modifying the global options when
> selecting with C-c @ and then exporting.
>
> The subtree options for example:
>
> #+EXPORT_OPTIONS: H:2 num:t toc:f \n:nil @:t ::t |:t ^:t -:t f:t *:t <:t
> TeX:t LaTeX:t skip:nil d:nil todo:t
Hello,
Charles Berry writes:
> I am trying to put together a derived backend that makes use of Src Block
> :parameters attribute.
>
> I can see that the header in a begin_src block is picked up by
>
> org-element-src-block-parser, as it should be when I try it interactively
>
> But not when I
When I input subtree options for modifying the global options when
selecting with C-c @ and then exporting.
The subtree options for example:
#+EXPORT_OPTIONS: H:2 num:t toc:f \n:nil @:t ::t |:t ^:t -:t f:t *:t <:t
TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:nil
#+EXPORT_FILE_NAME: tester
a
24 matches
Mail list logo
