Dear list,
using the latest version of org-mode I noticed that some of my larger
org files containing babel code caused emacs to segfault when doing an
incremental search. The culprit seems to be #+STARTUP: indent. I
managed to reproduce the bug using this minimal .emacs file:
(setq load-path (c
Hi Eric,
that may well be. I've now tried it on three machines, all 64-bit, and I
can reproduce the bug. Weird.
Cheers,
Per
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/
Hi,
I'm currently experimenting exporting notes from my beamer presentations
as articles via use of the beamerarticle package. In some cases, I only
want to export the *notes* to the article. This can be achieved easily
enough by setting #+SELECT_TAGS: B_noteNH B_note, but it would be a
hassle to
also pointed out at the end
of section 12.15, as I see now on closer inspection.
/P
Per Unneberg writes:
> Hi,
>
> I'm currently experimenting exporting notes from my beamer
> presentations as articles via use of the beamerarticle package. In
> some cases, I only want to expo
Hi,
I'm writing a custom function for use with a capture template, as
described in the section Template elements (sec 9.1.3.1) of the info
manual. My function does what I expect in that it finds the correct
heading (in my use case "Log") and returns point. However, if the Log
heading has no childr
Hi Eric,
Eric Abrahamsen writes:
> I'm messing about with some similar template-placement routines, so I
> tried your recipe below, and it worked for me... Capture by default
Odd, as I still can't get it to work. I tried it out with emacs -Q, just
defining that org-capture template and running
Hi list,
on exporting subtrees to latex, I've noticed that inserting several
EXPORT_LATEX_HEADER_EXTRA does not do what I naively had expected; that
each entry be inserted in the header, separated by a newline, along with
document properties (#+LATEX_HEADER et al). Looking closer at
org-export--ge
Hi,
Nicolas Goaziou writes:
>
> Yes, you cannot have duplicate property names in the same property
> drawer. OTOH you can append values to a property with :NAME+: syntax
> (e.g. :EXPORT_LATEX_HEADER+:). You can also try to make everything fit
> in a single line.
>
thanks for the clarifications a
Hi list,
in my configuration I require org-git-link to provide org links to
specific file versions. This means that for org-capture-templates, the
annotation "%a" will insert the org-git-link for org files under git
version control. However, I would like to insert the "usual" org link
("org" or "i
