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
On Wed, 4 Jul 2012 14:03:24 +1000
Jeffrey Spencer jeffspenc...@gmail.com wrote:
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
Hi Nicolas,
I have been trying out the `org-element-drag-backward' and
`org-element-drag-forward' navigation commands. I believe they stopped
working yesterday when I updated my org-mode (Git: dab2505 - a69f4b8).
When I try to move list items, I get the backtrace shown below. FWIW,
promotion and
On Tue, Jul 03, 2012 at 05:18:50PM -0700, Samuel Wales wrote:
On 7/3/12, Stefan Monnier monn...@iro.umontreal.ca 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.
Therefore, IF we have
I have agenda TODO items due in 5d (in org-upcoming-deadline face), in 16d (in
default face) and in 26d (in org-upcoming-deadline face).
Why is the 16d deadline in default face?
Eric S Fraga e.fraga at ucl.ac.uk writes:
A simple solution which keeps your interest in the outline structure at
this stage of the writing is to add the line
#+options: H:3
...
Thanks. That's a useful suggestion.
Sorry didn't finish the message.
That doesn't seem to work from what I have tried.
If for example it is
* 2012:noexport:
** June :noexport:
*** Not going output
*** Want to export this and subtrees :export:
Also export
The above example won't export anything because the
Hello,
suvayu ali fatkasuvayu+li...@gmail.com writes:
I have been trying out the `org-element-drag-backward' and
`org-element-drag-forward' navigation commands. I believe they stopped
working yesterday when I updated my org-mode (Git: dab2505 - a69f4b8).
When I try to move list items, I get
Hello,
This however didn't work for me. Since the beamer export is not in the
dispatcher yet, I tried the following:
* Lifetime acceptance WG update
:PROPERTIES:
:LaTeX_CLASS: beamer
:LaTeX_CLASS_OPTIONS: [presentation,smaller]
:EXPORT_FILE_NAME: WG_update.pdf
On Wed, Jul 4, 2012 at 5:56 PM, Nicolas Goaziou n.goaz...@gmail.com wrote:
Could you provide an ECM? I cannot reproduce the problem.
Also, is the move that you're trying to achieve allowed?
Yes the move is allowed. I can reproduce the problem with the attached
ECM. Evaluate the lisp block in a
Hello,
suvayu ali fatkasuvayu+li...@gmail.com writes:
Yes the move is allowed. I can reproduce the problem with the attached
ECM. Evaluate the lisp block in a minimal Emacs session and try to
reorder the list below with M-up/down.
I see. This behaviour is documented in `org-element-at-point'
Hi Nicolas,
On Wed, Jul 4, 2012 at 6:08 PM, Nicolas Goaziou n.goaz...@gmail.com wrote:
The exported latex source however has the following:
\documentclass[11pt]{article}
This is because LaTeX_CLASS and LaTeX_CLASS_OPTIONS properties are
not recognized as export properties. You have to use
Hi Nicolas,
On Wed, Jul 4, 2012 at 6:22 PM, Nicolas Goaziou n.goaz...@gmail.com wrote:
It means that if point is at the very beginning of the list, it will try
to move the whole list. Since there is nothing after the list, it
returns an error.
In order to drag the first item, you have to
The issue arises with org-agenda-redo. When running this command it selects
the last file that was used to make an agenda buffer. Since the previous
file used to do that was *SUMO* it tries to rebuild using that if currently
an *Org Agenda* buffer was open because this is the only time
Hello again,
Four months have passed and a lot of progress have been made. First I
suppressed the literate programming layer as it was getting too much in
the way.
Second, the support for the syntax has been greatly improved and
supports almost all constructions mentioned in org-element.el.
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
Charles Berry ccbe...@ucsd.edu writes:
I am trying to put together a derived backend that makes use of Src Block
:parameters attribute.
[deleted]
AFAICS :parameters is nowhere to be found when using
org-export-to-buffer.
This is
Hi List,
when I try out the function
,-
| (org-insert-todo-subheading ARG)
`-
with point at beginning-of-line of
,---
| * TODO
`---
and then
,---
| ** TODO
`---
no matter if I use 1, -1 or e.g. 'todo for
Thorsten Jolitz tjol...@googlemail.com writes:
#+begin_src org
*** TODO
** TODO
* TODO
#+end_src
Is that a bug - or am I using the function wrongly?
I would want the subheadings below the top-level
heading.
Answering my own question (by experimentation):
When point is on the *, the
Hi all,
there seems to be a bug in evaluating #+call lines.
To reproduce, consider this file:
,
| * Some Headline
| #+name: parameters
| #+BEGIN_SRC R
| ttt - 1
| #+END_SRC
|
| * Some Other Headline
| #+call: parameters() :results silent :exports none
`
and do C-c C-c on the #+call:
19 matches
Mail list logo
