clocking into an inline task before any headings

clocking into an inline task before any headings

[Myles English]

Hello,

Are inline tasks allowed to be used before any other headings?  (I hope
they are.)

Starting with

 $ emacs -Q

and with nothing more than a

 (require 'org-inlinetask)

I am able to insert an inline task with C-c C-x t but when I try to
clock in, "CLOCK:" is inserted on a line directly below the task title
and I get this Backtrace:

Debugger entered--Lisp error: (error "Before first headline at position 120 in buffer a.org")
  signal(error ("Before first headline at position 120 in buffer a.org"))
  error("Before first headline at position %d in buffer %s" 120 #<buffer a.org>)
  byte-code("\300\301`p#\207" [error "Before first headline at position %d in buffer %s"] 4)
  org-back-to-heading(t)
  org-narrow-to-subtree()
  org-clock-sum-current-item(nil)
  byte-code("\b?\205\a\306 \307\211\211\310	?\205\0\n\x1c\x1e@ABC\203=\x0eB\203+\x0eC\311=\203=\x0eD\204=	\204=\307\311D\312 \210)E\313\232\203N\311F\314\307G\"\210)E\315\232\203k\316\317!\211@\203g\320@!@\202k\321\322!\210E\323\232\203u\324 \210B\203\331\212@\204\204\325\311!\210\326H!@\203\224\326@!\202\225p\232\205\265\327H!@\203\251\327@!\202\252`U\205\265\x0eI\330\331 8\232)\203\304\332\333J\"\210\334\335\307\"\210K\327L!\326L!\223\210\311D\336\307\311\"\210)m\203\350\337 \204\350\340\341!\202\351`\212@\203\n\326@!\203\n\342\326@!!q\210\327@!\x0e@\307\211\223\210\212\214~\210b\210\325\311!\210B\204 \x0eK\307\211\223\210\212\307u\210\343\344!\210\345 \210)\346 \210\347M!\203P\350N!\210M\351\352!!\211O\203L\353O!\210)\202f\x0eM\203f\350P\354M\355R!\204f\353M!\210\350N!\205y\330\225\205y\356\357\225\330\225{!QR\203\215\347R!\203\215\x0eR \202\245\350N!\203\244\351\330!\203\244\360\361\362\351\330!#\202\245\363J\364J\365\307#J\366S!\210S\203\367\350\367T\370\371R!\203\367\332\372\351\357!\"\210\373\351\357!\374QA\357\225b\210\375\376\377\351\357!!\"U\201b`V\"W\201c\201d !X\202\256\x0eS\201e=\203\x02\332\201f!\210\201g \210\201h\352!\210\334\335\307\"\210\202\256\201i\201j!\210\201ku\210\201l \210\212\341\x7f\210\201m )\203H\201n\357!\210\201o\201p \352Z!\210T\201q\261\210\201b`V\"W\201c\201d !XF\203m\x0eG\206\236\v\203\225\201r\201s\201t\201u\201v !\201u\v!Z\201w\245\"!\203\225\v\206\236\x0eY\206\236\201v U\201x\x0eU\201y\201z#AL`\201{ \223\210H\212\325\311!\210`)\201{ \223\210\311Z[\201|=\204\333\x0e[\201}=\203\371\x0e\\\204\345\201~\x16\\\201\x7f\x0e\\>\204\371\201\200\x0e\\\201\201\"\\[\201\202=\204\v\x0e[\201}=\203\x03]^\201\203 \210_\203#\201\204\x0e_!\210\307_[\2034\201\205\x0e`\211\201\203#_a\203C\201\204\x0ea!\210\307a\201\205\201w\211\201\206#a\332\201\207\x0eA\f#\210\343\201\210!.	\207" [org-clock-resolving-clocks-due-to-idleness org-clock-resolving-clocks org-clock-leftover-time leftover msg-extra target-pos org-clocking-p nil "" t org-resolve-clocks (64) org-clock-in (4) org-clock-select-task "Clock-in on task: " copy-marker error "Abort" (16) org-clock-mark-default-task org-back-to-heading marker-buffer marker-position 4 org-heading-components message "Clock continues in \"%s\"" throw abort org-clock-out org-at-heading-p point-at-bol 0 org-base-buffer run-hooks org-clock-in-prepare-hook org-clock-history-push org-clock-set-current functionp looking-at match-string 2 org-todo "[ 	]*" "\\>" org-trim 1 replace-regexp-in-string "\\[\\[.*?\\]\\[\\(.*?\\)\\]\\]" ...] 7)
  org-clock-in(nil)
  call-interactively(org-clock-in nil nil)

This is the behaviour as of commit 75f73e0b87a.

Inserting a heading above the tasks allows it to be clocked into.

Thanks,

Myles

Re: clocking into an inline task before any headings

[Carsten Dominik]

On 14.8.2013, at 16:36, Myles English <mylesenglish@gmail.com> wrote:

> Hello,
> 
> Are inline tasks allowed to be used before any other headings?  (I hope
> they are.)

No, they are not.

Why don't you just make it a normal headline?

- Carsten

> 
> Starting with
> 
> $ emacs -Q
> 
> and with nothing more than a
> 
> (require 'org-inlinetask)
> 
> I am able to insert an inline task with C-c C-x t but when I try to
> clock in, "CLOCK:" is inserted on a line directly below the task title
> and I get this Backtrace:
> 
> Debugger entered--Lisp error: (error "Before first headline at position 120 in buffer a.org")
>  signal(error ("Before first headline at position 120 in buffer a.org"))
>  error("Before first headline at position %d in buffer %s" 120 #<buffer a.org>)
>  byte-code("\300\301`p#\207" [error "Before first headline at position %d in buffer %s"] 4)
>  org-back-to-heading(t)
>  org-narrow-to-subtree()
>  org-clock-sum-current-item(nil)
>  byte-code("\b?\205\a\306 \307\211\211\310	?\205\n\x1c\x1e@ABC\203=\x0eB\203+\x0eC\311=\203=\x0eD\204=	\204=\307\311D\312 \210)E\313\232\203N\311F\314\307G\"\210)E\315\232\203k\316\317!\211@\203g\320@!@\202k\321\322!\210E\323\232\203u\324 \210B\203\331\212@\204\204\325\311!\210\326H!@\203\224\326@!\202\225p\232\205\265\327H!@\203\251\327@!\202\252`U\205\265\x0eI\330\331 8\232)\203\304\332\333J\"\210\334\335\307\"\210K\327L!\326L!\223\210\311D\336\307\311\"\210)m\203\350\337 \204\350\340\341!\202\351`\212@\203\n\326@!\203\n\342\326@!!q\210\327@!\x0e@\307\211\223\210\212\214~\210b\210\325\311!\210B\204 \x0eK\307\211\223\210\212\307u\210\343\344!\210\345 \210)\346 \210\347M!\203P\350N!\210M\351\352!!\211O\203L\353O!\210)\202f\x0eM\203f\350P\354M\355R!\204f\353M!\210\350N!\205y\330\225\205y\356\357\225\330\225{!QR\203\215\347R!\203\215\x0eR \202\245\350N!\203\244\351\330!\203\244\360\361\362\351\330!#\202\245\363J\364J\365\307#J\366S!\210S\203\367\350\367T\370\371R!\203\367\332\372\351\357!\"\210\373\351\357!\374QA\357\225b\210\375\376\377\351\357!!\"U\201b`V\"W\201c\201d !X\202\256\x0eS\201e=\203\x02\332\201f!\210\201g \210\201h\352!\210\334\335\307\"\210\202\256\201i\201j!\210\201ku\210\201l \210\212\341\x7f\210\201m )\203H\201n\357!\210\201o\201p \352Z!\210T\201q\261\210\201b`V\"W\201c\201d !XF\203m\x0eG\206\236\v\203\225\201r\201s\201t\201u\201v !\201u\v!Z\201w\245\"!\203\225\v\206\236\x0eY\206\236\201v U\201x\x0eU\201y\201z#AL`\201{ \223\210H\212\325\311!\210`)\201{ \223\210\311Z[\201|=\204\333\x0e[\201}=\203\371\x0e\\\204\345\201~\x16\\\201\x7f\x0e\\>\204\371\201\200\x0e\\\201\201\"\\[\201\202=\204\v\x0e[\201}=\203\x03]^\201\203 \210_\203#\201\204\x0e_!\210\307_[\2034\201\205\x0e`\211\201\203#_a\203C\201\204\x0ea!\210\307a\201\205\201w\211\201\206#a\332\201\207\x0eA\f#\210\343\201\210!.	\207" [org-clock-resolving-clocks-due-to-idleness org-clock-resolving-clocks org-clock-leftover-time leftover msg-extra target-pos org-clocking-p nil "" t org-resolve-clocks (64) org-clock-in (4) org-clock-select-task "Clock-in on task: " copy-marker error "Abort" (16) org-clock-mark-default-task org-back-to-heading marker-buffer marker-position 4 org-heading-components message "Clock continues in \"%s\"" throw abort org-clock-out org-at-heading-p point-at-bol 0 org-base-buffer run-hooks org-clock-in-prepare-hook org-clock-history-push org-clock-set-current functionp looking-at match-string 2 org-todo "[ 	]*" "\\>" org-trim 1 replace-regexp-in-string "\\[\\[.*?\\]\\[\\(.*?\\)\\]\\]" ...] 7)
>  org-clock-in(nil)
>  call-interactively(org-clock-in nil nil)
> 
> This is the behaviour as of commit 75f73e0b87a.
> 
> Inserting a heading above the tasks allows it to be clocked into.
> 
> Thanks,
> 
> Myles
> 

Re: clocking into an inline task before any headings

[Myles English]

Hi Carsten,

Carsten Dominik writes:

> On 14.8.2013, at 16:36, Myles English <mylesenglish@gmail.com> wrote:
>
>> Are inline tasks allowed to be used before any other headings?  (I hope
>> they are.)
>
> No, they are not.
>
> Why don't you just make it a normal headline?

Okay, I can put the inline task under a normal headline with a
:noheading: tag that causes a filter to omit the headline itself, and
this is good enough for my needs:

* Like This                       :noheading:

*************** TODO Something inline
*************** END

Just to explain what I am doing though: writing a report, e.g.:

* Introduction
* Method
* Conclusions

Adding tasks as headings breaks up the structure undesirably:

* TODO Decide on a layout for the whole document
* Introduction
* TODO Finish writing the introduction
* Method
* Conclusions

Alternatively, using inline tasks, the document structure is still easy
to see (scanning down the left side) and they fold nicely:

*************** TODO Decide on a layout for the whole document...
* Introduction
*************** TODO Finish writing the introduction...
* Method
* Conclusions

Labouring the point at bit, I see the headlines as the fingers on my
left hand and the inline tasks are the fingers on my right hand and they
interleave:

*************** TODO Decide on a layout for the whole document...
* Introduction
*************** TODO Finish writing the introduction...
* Method
** Setup
*** Safety
*************** TODO Add fire exits...
**** Insurance
*************** TODO Ring broker...
* Conclusions

Changing the inline task before the Introduction to be under a headline
works but breaks up the document a little at the start:

* First task                                       :noheading:
*************** TODO Decide on a layout for the whole document...
* Introduction
*************** TODO Finish writing the introduction...
* Method
** Setup
*** Safety
*************** TODO Add fire exits...
**** Insurance
*************** TODO Ring broker...
* Conclusions

(Another issue that may be related to this is that the preamble in a
complicated document for LaTeX export takes up a whole screen and it
would be nice to be able to fold it.)

Thanks,

Myles