[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] Using the file as 1st level headline

From: Sven Bretfeld
Subject: Re: [O] Using the file as 1st level headline
Date: Thu, 17 Sep 2015 19:55:07 +0200

Hi Eric

Eric S Fraga writes:

> On Wednesday, 16 Sep 2015 at 18:49, Sven Bretfeld wrote:

>> Is it possible to have a file header which is counted as a first level
>> headline? 
> I am not sure how this relates to the rest of your email.  Can you
> please expand on this?

I should have been more clear. The problem is the project definition. It
will become clear below.

>> Now, I'm using org to write scientific books and articles. Therefore,
>> I want to use 1st level headlines as section titles for LaTeX export.
>> Of course, not every section is an individual project---the article in
>> total is the project and its doable steps are defined by inline tasks.
>> So, what I want to do is something like this:
> Have you actually tried what you wrote?  What happens?

If I do it that way, each inline-task is treated as a standalone task,
not as subtask of a larger project. One of the strengths of Bernt
Hansen's setup is the possibility to narrow down the agenda to a
specific project and have only its next steps and other subtasks
displayed. A project is defined as a headline with TODO keyword which
has at least one sublevel headline also containing a TODO keyword. An
inline-task inside a standard article structure has no higher level task
which would count as the project subsuming the inline-tasks as subtasks.

At the moment I'm using this solution:

* TODO Introduction
********************* NEXT Something 1
********************* END

* TODO Chapter 1
******************** TODO Something 2
******************** END

But this makes "Introduction" and "Chapter 1" individual projects and
assigns a single subtask to each named "Something 1" and "Something 2".
For a book this can easily sum up to 20 different "projects" (i.e.
chapters) which mess up the agenda-view and the work-flow. What would
work is:

* TODO Write book on XY
** Introduction
********************* NEXT Something 1
********************* END

** Chapter 1
******************** TODO Something 2
******************** END
But this collides with the export, as it turns the chapters into
subchapters. So "Introduction" would be 1.1 instead of 1. Furthermore,
this is confusing while working on the file. Therefore I was asking if
it's possible to assign a TODO keyword to the file itself via a header
which would, then, play the role of the project definition subsuming the
inline-tasks as subtasks.

The only other way would be a redefinition of what a project is. But my
lisp knowledge is by far overstrained with this. Basically I'm happy
with the TODO-subTODO approach. So it must be a complimentary definition
saying basically: "All TODO lines in file xy.org are treated as subtasks
to the project `Write book on XY'".

> Is the issue, in your case, that the noexport tag on the inlinetasks is
> ignored?  If so, you could simply define the org-latex-format-inlinetask
> function I have above to do nothing?

No, that's not the problem. I, too, include them in the export when I
need them printed. Sorry, I should have been more clear in the first

Thanks for help,


Sven Bretfeld
Department of Philosophy and Religious Studies
NTNU Trondheim

reply via email to

[Prev in Thread] Current Thread [Next in Thread]