[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Orgmode] Re: How to define TODOs within continuous text the best way?
From: |
Bernt Hansen |
Subject: |
[Orgmode] Re: How to define TODOs within continuous text the best way? |
Date: |
Mon, 30 Mar 2009 16:18:01 -0400 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) |
Carsten Dominik <address@hidden> writes:
> Sometimes, miracles do happen.
:)
<snip>
> Fool the user, not Org!
>
> We will make them just normal outline nodes with stars,
> metadata and all the rest. Full citizens. But then we treat
> them specially in just two situations:
>
> 1. For visibility cycling: We disqualify these tasks from being
> recognized during visibility cycling. Simply by setting a
> limit for the outline depth to be seen by cycling, treating
> any deeper levels as normal text. So if the parent opens, all
> these "disqualified" nodes are treated as text and open as
> well.
>
> 2. During export: We treat the node and its meta data as special
> and export it as some inline construct, and we do this in the
> export *preprocessor* already, so that the backends never know
> there was an outline node at all. This fixes any issues with
> section numbering, text and list continuation etc.
>
> 3. As icing on the cake we introduce special fontification which
> make inline tasks look deeply indented.
>
> I have put these features into a new add-on, org-inlinetask.el.
> Just (require 'org-inlinetask) should turn it on for you, and
> any headline with a level 15 or deeper (30 if you use odd levels
> only) will then be subject to the special treatment.
>
> I just pushed this file into the git repository. Read the file
> commentary for explanations and try it out - I think the
> mechanism work surprisingly well.
>
> I simply cannot believe that after all those years, we might be
> able to close this task.
I think there's a bug here. I have started using
(setq org-odd-levels-only t)
again and org-cycle() complains about 'limit' not having a value.
,----[ org.el line 4533 ]
| (and limit-level (1- (* limit 2)))
`---- ^^^^^
All I did was update to the latest version in git and did not make any
other changes to my setup (ie. I'm not using the
(require 'org-inlinetask)
stuff)
I'm not sure what this is supposed to be..
Here's the backtrace.
-Bernt
Debugger entered--Lisp error: (void-variable limit)
(* limit 2)
(1- (* limit 2))
(and limit-level (1- (* limit 2)))
(if org-odd-levels-only (and limit-level (1- ...)) limit-level)
(and limit-level (if org-odd-levels-only (and limit-level ...) limit-level))
(let* ((limit-level ...) (nstars ...) (outline-regexp ...) (bob-special ...)
(org-cycle-hook ...) (pos ...)) (if (or bob-special ...) (setq arg t)) (cond
(... ... ...) (... ... ...) (... ...) (... ...) (... ...) (... ...) (... ...
...) (buffer-read-only ...) (...) (...) (... ...) (... ...) (t ...)))
org-cycle(nil)
call-interactively(org-cycle)
recursive-edit()
byte-code("Æ @Ç=! ÈÉÊ\"ËÉ!A@)¢Ì=! ÈÍÊ\"Î!Ï Ð !\fc Ñed\"
VW ebÒ
¥y`dbÒ
¥
Zy`|)ÓcebÔÕÖ \"× ÔØ!ÙÊÔØ!Ú +Ù" [unread-command-char
debugger-args x debugger-buffer noninteractive debugger-batch-max-lines -1
debug backtrace-debug 4 t backtrace-frame lambda 5 pop-to-buffer debugger-mode
debugger-setup-buffer count-lines 2 "...\n" message "%s" buffer-string
kill-emacs "" nil recursive-edit middlestart buffer-read-only standard-output]
4)
debug(error (void-variable limit))
(* limit 2)
(1- (* limit 2))
(and limit-level (1- (* limit 2)))
(if org-odd-levels-only (and limit-level (1- ...)) limit-level)
(and limit-level (if org-odd-levels-only (and limit-level ...) limit-level))
(let* ((limit-level ...) (nstars ...) (outline-regexp ...) (bob-special ...)
(org-cycle-hook ...) (pos ...)) (if (or bob-special ...) (setq arg t)) (cond
(... ... ...) (... ... ...) (... ...) (... ...) (... ...) (... ...) (... ...
...) (buffer-read-only ...) (...) (...) (... ...) (... ...) (t ...)))
org-cycle(nil)
call-interactively(org-cycle)
recursive-edit()
byte-code("Æ @Ç=! ÈÉÊ\"ËÉ!A@)¢Ì=! ÈÍÊ\"Î!Ï Ð !\fc Ñed\"
VW ebÒ
¥y`dbÒ
¥
Zy`|)ÓcebÔÕÖ \"× ÔØ!ÙÊÔØ!Ú +Ù" [unread-command-char
debugger-args x debugger-buffer noninteractive debugger-batch-max-lines -1
debug backtrace-debug 4 t backtrace-frame lambda 5 pop-to-buffer debugger-mode
debugger-setup-buffer count-lines 2 "...\n" message "%s" buffer-string
kill-emacs "" nil recursive-edit middlestart buffer-read-only standard-output]
4)
debug(error (void-variable limit))
(* limit 2)
(1- (* limit 2))
(and limit-level (1- (* limit 2)))
(if org-odd-levels-only (and limit-level (1- ...)) limit-level)
(and limit-level (if org-odd-levels-only (and limit-level ...) limit-level))
(let* ((limit-level ...) (nstars ...) (outline-regexp ...) (bob-special ...)
(org-cycle-hook ...) (pos ...)) (if (or bob-special ...) (setq arg t)) (cond
(... ... ...) (... ... ...) (... ...) (... ...) (... ...) (... ...) (... ...
...) (buffer-read-only ...) (...) (...) (... ...) (... ...) (t ...)))
org-cycle(nil)
call-interactively(org-cycle)
yas/expand()
call-interactively(yas/expand)
- [Orgmode] How to define TODOs within continuous text the best way?, Karl Maihofer, 2009/03/28
- Re: [Orgmode] How to define TODOs within continuous text the best way?, Sebastian Rose, 2009/03/28
- Re: [Orgmode] How to define TODOs within continuous text the best way?, Sebastian Rose, 2009/03/28
- Re: [Orgmode] How to define TODOs within continuous text the best way?, Carsten Dominik, 2009/03/30
- [Orgmode] Re: How to define TODOs within continuous text the best way?,
Bernt Hansen <=
- Re: [Orgmode] How to define TODOs within continuous text the best way?, Karl Maihofer, 2009/03/31
- Re: [Orgmode] How to define TODOs within continuous text the best way?, Daniel Clemente, 2009/03/31