Jacob Gerlach | 27 Apr 20:29 2015

[BUG?] Blank line required between text and short caption


Is it required by org syntax to separate short captions from body text?

In the following example:
Some text that introduces this table.
#+CAPTION[Short caption]:
#+CAPTION: Longer caption
| Foo |

Latex export gives:
Some text that introduces this table.
\#+CAPTION[Short caption]:
\caption{Longer caption}

Adding an empty line between the text and short caption produces the
expected results:
Some text that introduces this table.

#+CAPTION[Short caption]:
(Continue reading)

Lawrence Bottorff | 27 Apr 20:12 2015

Latex export or Latex tangle? Best practice?

In a previous post I was getting at the issue of whether I should just do regular export or use latex "code blocks" for what I wanted in a final document. What I want is the ability to create a big, rambling, annotated org file -- with "keeper" stuff inside the latex babel blocks -- then tangle the .org file, thereby leaving all the annotations and lead-up notes behind. I'm sure I'm not alone in wanting "notes" to evolve into a "finished product" and orgmode would seem to offer a good path. So, I don't want to have to hand-edit out my so-called annotations. Is keeping the good stuff in latex babel blocks a best practice?

Renato | 23 Apr 23:21 2015

Re: Bug: Priority #B in Agenda causes invalid face reference [8.2.1 (8.2.1-15-ge5cecc-elpa <at> /Users/Paul/.emacs.d/elpa/org-20131021/)]

I'm using release_8.2.10 and experienced the same problem.

The problem seems to be the function org-agenda-fontify-priorities which
		       'priority nil
		       (cdr (assoc p org-priority-faces)))

which expects a face to inherit from. When org-priority-faces is nil or
color or even does not specify the priority(e.g. "B") it inherits from
nil and causes the message.
Setting it to something like 
    ((65 . org-level-1)
     (66 . org-level-2)
     (67 . org-level-3)
     (68 . org-level-4))))

is a workaround to the problem.


Daniele Pizzolli | 27 Apr 17:47 2015

BUG: named time references problem in formula


according to [[info:org#References]] (see Named references) is possible
to use a property in formulas. This generally works, but not when the
property is a time value as defined in

Please have a look at the following ECM:

* test table with constant (working)
   :constant: 3

| month |  days | results |
|    01 |     1 |       3 |
|    02 |     3 |       9 |
#+TBLFM: $3=$2*$PROP_constant;

* test table with time constant (not working)
   :time_constant: 08:00:00

| month | days | time |
|    01 |    1 |      |
|    02 |    3 |      |
#+TBLFM: $3=$2*$PROP_time_constant;T

Pressing C-u C-c C-c over the table shows in the message buffer:

org-table-eval-formula: Wrong type argument: stringp, (13 "Bad format")

Also is not possible to debug the code even with the formula debug

Omitting the ";T" part will cause the debug to work and then the string
#ERROR show up in the cell.

My version is Org-mode version 8.3beta (release_8.3beta-1080-g367d48  <at> 


Detlef Steuer | 27 Apr 16:59 2015

#+LINK abbrevs possible in #+INCLUDEs ?


Emacs and git in today´s fresh version.

I have two files:

#+LINK: HOME http://example.de

* My Homepage
  You can find my homepage [[HOME][here]]

#+INCLUDE: file2.org

#+LINK: HOME2 http://other.example.de

* My other page
  You can find my other page [[HOME2][here]]

I can export file2.org to html as expected.

I can´t export file1.org to html with the included file2.org.
Only if I move the #+LINK line from file2 to file1 the export
works as expected.

In my setting file2.org must export standalone, so moving the LINKs to
file1 is no option. An ugly workaround would be to include the
abbreviation for HOME2 in both files.  Ugly.

Is there a woraround/setting to have local #+LINK directives working in
included files? 


Zhihao Ding | 27 Apr 16:47 2015

navigate between source code blocks

Dear Org experts, 

I’ve got a simple question: how to speed up jumping 
between code blocks? 

My org file grows larger every day with more and more
source code blocks. I find myself spending increasing 
amount of time finding the right code blocks to go to. 

Could anyone suggest a method to increase efficiency?
So far I’ve tried (1)  simple search and (2) C-c C-v g, 
which for some reason often fails to find blocks. 

Thanks very much!


Traycer Bullet | 27 Apr 04:21 2015

custom agenda view not possible?

I'm transitioning from a web-based to-do list, and one thing I rely on is viewing recently CREATED or CLOSED tasks, e.g. within the last 2 days.  My hope is to recreate this with a custom agenda view, but I haven't been able to find the correct commands/filters.  Keeping in mind I'm new to Emacs/Lisp/OrgMode, here's what I've tried so far (for just the CLOSED example):

This doesn't work because tags-todo excludes 'DONE' status tasks:
(add-to-list 'org-agenda-custom-commands
             '("J" "Completed Recently" tags-todo "CLOSED>=\"<-2d>\""))

This doesn't work because the org-agenda-tag-filter-preset only works for tags:
(add-to-list 'org-agenda-custom-commands
            '("J" "Completed Recently" todo "DONE"
              ((org-agenda-tag-filter-preset '("+CLOSED>=\"<-2d>\"")))))

Regarding the desired CREATED agenda view, I use a script to add a CREATED timestamp as property to each task (see: http://stackoverflow.com/questions/12262220/add-created-date-property-to-todos-in-org-mode ), so a task will look something like this:

TODO  New task for today
  :CREATED:  [2015-04-13 Mon 17:57]

There is no agenda filtering preset options for Properties (only tags/category/regexp), which is the only way I could think of to do the necessary date comparisons (e.g. <-2d>).

The task seems simple, so I'm hopeful I'm overlooking some way of accomplishing it.  
Lawrence Bottorff | 27 Apr 01:20 2015

Tangled Latex code gives error

I'm following the Latex howto of org-mode babel. Here's the snippet from the howto I've got in a separate .org file (see bottom of howto page):

#+LATEX_HEADER: \usepackage{tikz}

First execute the second code block, to define the convenience macro
and to set the required new variables in ob-latex.el.  Then export to
HTML and to pdf to see the tree exported as an SVG image and as
embedded tikz respectively.

* Tikz test
Here's a tree, exported to both html and pdf.

#+header: :file (by-backend (html "tree.svg") (t 'nil))
#+header: :imagemagick
#+header: :results (by-backend (pdf "latex") (t "raw"))
#+header: :tangle yes
#+begin_src latex
    \node [circle, draw, fill=red!20] at (0,0) {1}
    child { node [circle, draw, fill=blue!30] {2}
      child { node [circle, draw, fill=green!30] {3} }
      child { node [circle, draw, fill=yellow!30] {4} }};

* COMMENT setup
#+header: :tangle yes
#+begin_src emacs-lisp :results silent
  (setq org-babel-latex-htlatex "htlatex")
  (defmacro by-backend (&rest body)
    `(case (if (boundp 'backend) (org-export-backend-name backend) nil) , <at> body))

This doesn't really produce a .svg of the tree as advertised, but exporting to Latex does produce it just fine.

My real confusion starts when I try to tangle the babel code blocks. The C-c C-v t command produces two separate files just fine, a .tex and .el, but then if I try to Run Latex on the .tex file just by itself it gives an error. Here's what the org-mode tangle produces:

  \node [circle, draw, fill=red!20] at (0,0) {1}
  child { node [circle, draw, fill=blue!30] {2}
    child { node [circle, draw, fill=green!30] {3} }
    child { node [circle, draw, fill=yellow!30] {4} }};

And here's the error log after I try to run it by itself in Emacs:

. . .entering extended mode
 restricted \write18 enabled.
 file:line:error style messages enabled.
 %&-line parsing enabled.
**\input prac2.tex
./prac2.tex:2: Undefined control sequence.
l.2 \usetikzlibrary
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
Another version (from C-c `) produces this error message:

ERROR: Undefined control sequence.

--- TeX said ---
l.2 \usetikzlibrary
--- HELP ---
TeX encountered an unknown command name. You probably misspelled the
name. If this message occurs when a LaTeX command is being processed,
the command is probably in the wrong place---for example, the error
can be produced by an \item command that's not inside a list-making
environment. The error can also be caused by a missing \documentclass

What am I missing here? I'd like to be able to keep my org stuff separate from the Latex source, which org-mode seems to do nicely. But then it has to run properly too. . . .

David Dynerman | 27 Apr 00:39 2015

Conditional .gitignore for org-mode files

Hi all,

Sorry in advance, this might be more of a git question than an org-mode
question, but I thought someone on this list might know the answer.

Is it possible to conditionally gitignore certain files based on files
that are being tracked?

What I'd like is something like the following gitignore logic:

if filename.org is tracked by git:
   ignore filename.tex, filename.html

If this isn't possible, does anyone have any nice setups for ignoring
exported versions of org-mode files?


Thomas S. Dye | 27 Apr 01:03 2015

Org-lint and #+call lines

Aloha all,

Org-lint is a big help picking up an old project.  Thanks Nicolas.

The original patch sent to the ML ran through my old org mode file and
found lots of potential problems.

So, I decided to track wip-lint.  Now, the linting stops with this

| Org linting process starting...                        
| let: Wrong type argument: listp, ":results replace org"

The *Org Lint* buffer is empty, except for the header line.

Here is the offending line in the Org mode file:

| #+call: r-duplicate-ids() :results replace org

All the best,


Thomas S. Dye

Joon Ro | 26 Apr 21:35 2015

export fails with "byte-code: Before first headline at position ..."


When I try to export my org files I'm getting this error. For example:

byte-code: Before first headline at position 1 in buffer Blog.org<2>

I could not find any way to fix this - any help will be very appreciated.

Thank you,