Alan E. Davis wrote:
I don't understand why I do not see "section" or "subsection", and the
sections often come out with bare stars. Is this also because the
number of levels has been exceeded?
Are you, by any chance, using a top-level org file with
#+INCLUDE lines? If so, you need to
On May 21, 2009, at 10:14 PM, Alan E. Davis wrote:
Thank you for the response.
On May 21, 2009, at 4:27 PM, Carsten Dominik wrote:
The only thing you can do in Org is to increase the number of
headline levels to the maximum possible:
#+OPTION H:5
This doesn't work for me.
Typo:
#+OP
Gray,
Yes, exporting will convert those variables inline, however, you could
include an area to define them in your header. Then again, if thats
the case, you may just want to stick to adding them into #+LATEX_HEADER.
On Thu, May 21, 2009 at 10:08:21PM +, Gray Calhoun wrote:
> > On Thu, May 2
> On Thu, May 21, 2009 at 05:13:41PM +, Gray Calhoun wrote:
> > I'd like to define LaTeX macros that display correctly when they're
> > embedded in an org file and are preserved when I export that file to LaTeX.
> > Right now, I've added the LaTeX macros to org-format-latex-header, and
> >
I'm quite new to org-mode, and have only recently begun using emacs
again (after an absence of 15 years or so..) so excuse the newbie
question...
Is it possible to hide, during normal editing, the configuration /
comment lines in a project file?
TIA,
Keith Lancaster
klancaster1...@mac.com
Thank you for the response.
> On May 21, 2009, at 4:27 PM, Carsten Dominik wrote:
>
>>
>> The only thing you can do in Org is to increase the number of headline
>> levels to the maximum possible:
>>
>> #+OPTION H:5
>
>
This doesn't work for me.
>
>> is I think the maximum you can get. You cal
Couldn't you use the {{{macro}}} expansion in the export header? I
believe you can make your own.
On Thu, May 21, 2009 at 05:13:41PM +, Gray Calhoun wrote:
> Hi Everyone,
>
> I'd like to define LaTeX macros that display correctly when they're
> embedded in an org file and are preserved when
Alan's request for a different LaTeX heading export made me think of this.
If what you want is deeply nested outlines in LaTeX, checkout the
'easylist' package for LaTeX on CTAN, It takes what amounts to
org-style outlines (where subordination is indicated by increasing the
number of a given prefi
Hi Everyone,
I'd like to define LaTeX macros that display correctly when they're
embedded in an org file and are preserved when I export that file to LaTeX.
Right now, I've added the LaTeX macros to org-format-latex-header, and
repeated the macros in a #+LATEX_HEADER: comment. The two drawbac
Replying to my own message:
On May 21, 2009, at 4:27 PM, Carsten Dominik wrote:
Hi Alan,
this is a fundamental limitation in LaTeX
See http://www.tex.ac.uk/cgi-bin/texfaq2html?label=toodeep
The only thing you can do in Org is to increase the number of
headline levels to the maximum possibl
I was wondering if possibly anyone has created a bash
script/python/anything to produce an iCal export from a bunch of
org-files? I would like to fire up a cron job to export a list
periodically and find that emacs batch is a tad heavy and some issues
with my emacs 23 often means it falls over whe
Hi Alan,
this is a fundamental limitation in LaTeX
See http://www.tex.ac.uk/cgi-bin/texfaq2html?label=toodeep
The only thing you can do in Org is to increase the number of headline
levels to the maximum possible:
#+OPTION H:5
is I think the maximum you can get. You cal also create a
LaTeX
An outline, when exported as PDF, shows no sections. When exporting to
LaTeX, the following message is received:
ERROR: LaTeX Error: Too deeply nested.
--- TeX said ---
See the LaTeX manual or LaTeX Companion for explanation.
Type H for immediate help.
...
l.110 \begin{ite
Ah.
My bad. Of course that's not how to set the property.
#+PROPERTY: COOKIE_DATA recursive
works great.
Alexander
On 5/21/09, Carsten Dominik wrote:
>
> On May 20, 2009, at 2:59 PM, Alexander wrote:
>
>> Thanks!
>>
>> It works great. However, I can't get it to work on a per-file basis,
>> ie
On May 21, 2009, at 9:23 AM, Mikael Fornius wrote:
Carsten Dominik writes:
I have applied this patch, thank you for your contribution!
My pleasure.
No hurry, better to get it complete and tested...
:-)
I should have read this advice more carefully :-)
:-)
Applied, thanks.
- Cars
Carsten Dominik writes:
> I have applied this patch, thank you for your contribution!
My pleasure.
> No hurry, better to get it complete and tested...
> :-)
I should have read this advice more carefully :-)
Because before, when only sums where calculated as summaries, 0 was
placed instead of
On May 19, 2009, at 6:28 PM, Samuel Wales wrote:
On 2009-05-18, Carsten Dominik wrote:
I have now changed this so that it is parallel to what happens
durng all other export types: The exported buffer stays hidden
when you do `C-c C-e a'. Realizing that often you'd
want to paste this stuff,
17 matches
Mail list logo
