Re: [O] Sticky agenda branch merged
Rainer Stengele writes: > Am 17.04.2012 12:09, schrieb Rainer Stengele: > Hi Max, > > I found the culprit: > > > (defun bh/mark-parent-tasks-started () > "Visit each parent task and change TODO states to STARTED" > (unless bh/mark-parent-tasks-started > (when (equal state "INARBEIT") > (let ((bh/mark-parent-tasks-started t)) > (save-excursion > (while (org-up-heading-safe) > (when (member (nth 2 (org-heading-components)) (list "TODO" > "INARBEIT" "WARTEN")) > (org-todo "INARBEIT" > > (add-hook 'org-after-todo-state-change-hook 'bh/mark-parent-tasks-started > 'append) > > > something seems to have changed conecerning the "state" variable. The > function fails and stops the clockin process. > Deactivating the hook brings back the right behaviour. > Sorry for that. > > Bernt, that function of yours does seem to have stopped working? Hi Rainer, I no longer use a STARTED state so I've dropped this function from my setup. I'll update the doc - thanks for the notification. Regards, Bernt
Re: [O] Sticky agenda branch merged
Am 17.04.2012 21:35, schrieb Nick Dokos: > Rainer Stengele wrote: > >> Am 17.04.2012 12:09, schrieb Rainer Stengele: >>> Am 16.04.2012 11:47, schrieb Max Mikhanosha: I had just pushed a merge of max-sticky-agenda branch to master, let me know if there are any problems, also feel free to hack/iterate on it, if you have question as to why something was done, I'll do my best to answer. In particular I just seen a new commit introducing filter on categories, and org-agenda-filtered-by-top-category probably needs to be included into local variable list to have it work per agenda buffer. Also the individual calls to org-todo-list and such, do not work right with sticky agenda as there is nothing to catch the 'exit tag, that is thrown by `org-prepare-agenda' when it finds cached buffer. I'm not sure there is more elegant way of fixing it, other then wrapping all the individual scanner pieces with (catch) blocks, that re-throw if they had detected that they been called from (org-agenda) command Regards, Max >>> Hi, >>> >>> I see a strange behaviour when clocking in with C-c C-x C-i. >>> Sometimes (!) there is no new CLOCK: entry created. >>> The TODO state changes as expected, but no new CLOCK: line is created, even >>> when clocking out. >>> Looks like this happens when the initial TODO state is set. >>> >>> Maybe I missed a change in the behaviour? >>> >>> Regards, >>> Rainer >>> >>> >> Hi Max, >> >> I found the culprit: >> >> >> (defun bh/mark-parent-tasks-started () >>"Visit each parent task and change TODO states to STARTED" >>(unless bh/mark-parent-tasks-started >> (when (equal state "INARBEIT") >>(let ((bh/mark-parent-tasks-started t)) >> (save-excursion >>(while (org-up-heading-safe) >> (when (member (nth 2 (org-heading-components)) (list "TODO" >> "INARBEIT" "WARTEN")) >>(org-todo "INARBEIT" >> >> (add-hook 'org-after-todo-state-change-hook 'bh/mark-parent-tasks-started >> 'append) >> >> something seems to have changed conecerning the "state" variable. > > Presumably another victim of the variable renaming patches. Try > renaming "state" to "org-state" and see if that works (untested, > no promises). > > Nick > > >> The function fails and stops the clockin process. Deactivating the >> hook brings back the right behaviour. Sorry for that. > >> >> Bernt, that function of yours does seem to have stopped working? >> >> Thanks and regards, >> Rainer >> > > Yep, "org-state" works. Sorry, I missed the renaming tale. Thanks a lot, Nick! Rainer
Re: [O] Sticky agenda branch merged
Rainer Stengele wrote: > Am 17.04.2012 12:09, schrieb Rainer Stengele: > > Am 16.04.2012 11:47, schrieb Max Mikhanosha: > >> I had just pushed a merge of max-sticky-agenda branch to master, let > >> me know if there are any problems, also feel free to hack/iterate on > >> it, if you have question as to why something was done, I'll do my best > >> to answer. > >> > >> In particular I just seen a new commit introducing filter on > >> categories, and org-agenda-filtered-by-top-category probably needs to > >> be included into local variable list to have it work per agenda > >> buffer. > >> > >> Also the individual calls to org-todo-list and such, do not work right > >> with sticky agenda as there is nothing to catch the 'exit tag, that is > >> thrown by `org-prepare-agenda' when it finds cached buffer. I'm not > >> sure there is more elegant way of fixing it, other then wrapping all > >> the individual scanner pieces with (catch) blocks, that re-throw if > >> they had detected that they been called from (org-agenda) command > >> > >> Regards, > >>Max > >> > >> > > Hi, > > > > I see a strange behaviour when clocking in with C-c C-x C-i. > > Sometimes (!) there is no new CLOCK: entry created. > > The TODO state changes as expected, but no new CLOCK: line is created, even > > when clocking out. > > Looks like this happens when the initial TODO state is set. > > > > Maybe I missed a change in the behaviour? > > > > Regards, > > Rainer > > > > > Hi Max, > > I found the culprit: > > > (defun bh/mark-parent-tasks-started () >"Visit each parent task and change TODO states to STARTED" >(unless bh/mark-parent-tasks-started > (when (equal state "INARBEIT") >(let ((bh/mark-parent-tasks-started t)) > (save-excursion >(while (org-up-heading-safe) > (when (member (nth 2 (org-heading-components)) (list "TODO" > "INARBEIT" "WARTEN")) >(org-todo "INARBEIT" > > (add-hook 'org-after-todo-state-change-hook 'bh/mark-parent-tasks-started > 'append) > > something seems to have changed conecerning the "state" variable. Presumably another victim of the variable renaming patches. Try renaming "state" to "org-state" and see if that works (untested, no promises). Nick > The function fails and stops the clockin process. Deactivating the > hook brings back the right behaviour. Sorry for that. > > Bernt, that function of yours does seem to have stopped working? > > Thanks and regards, > Rainer >
Re: [O] Sticky agenda branch merged
Am 17.04.2012 12:09, schrieb Rainer Stengele: Am 16.04.2012 11:47, schrieb Max Mikhanosha: I had just pushed a merge of max-sticky-agenda branch to master, let me know if there are any problems, also feel free to hack/iterate on it, if you have question as to why something was done, I'll do my best to answer. In particular I just seen a new commit introducing filter on categories, and org-agenda-filtered-by-top-category probably needs to be included into local variable list to have it work per agenda buffer. Also the individual calls to org-todo-list and such, do not work right with sticky agenda as there is nothing to catch the 'exit tag, that is thrown by `org-prepare-agenda' when it finds cached buffer. I'm not sure there is more elegant way of fixing it, other then wrapping all the individual scanner pieces with (catch) blocks, that re-throw if they had detected that they been called from (org-agenda) command Regards, Max Hi, I see a strange behaviour when clocking in with C-c C-x C-i. Sometimes (!) there is no new CLOCK: entry created. The TODO state changes as expected, but no new CLOCK: line is created, even when clocking out. Looks like this happens when the initial TODO state is set. Maybe I missed a change in the behaviour? Regards, Rainer Hi Max, I found the culprit: (defun bh/mark-parent-tasks-started () "Visit each parent task and change TODO states to STARTED" (unless bh/mark-parent-tasks-started (when (equal state "INARBEIT") (let ((bh/mark-parent-tasks-started t)) (save-excursion (while (org-up-heading-safe) (when (member (nth 2 (org-heading-components)) (list "TODO" "INARBEIT" "WARTEN")) (org-todo "INARBEIT" (add-hook 'org-after-todo-state-change-hook 'bh/mark-parent-tasks-started 'append) something seems to have changed conecerning the "state" variable. The function fails and stops the clockin process. Deactivating the hook brings back the right behaviour. Sorry for that. Bernt, that function of yours does seem to have stopped working? Thanks and regards, Rainer
Re: [O] Sticky agenda branch merged
Am 17.04.2012 17:32, schrieb Max Mikhanosha: Hi Rainer, At Tue, 17 Apr 2012 15:23:00 +0200, Rainer Stengele wrote: Am 17.04.2012 14:29, schrieb Max Mikhanosha: At Tue, 17 Apr 2012 12:09:40 +0200, Rainer Stengele wrote: Am 16.04.2012 11:47, schrieb Max Mikhanosha: I had just pushed a merge of max-sticky-agenda branch to master, let me know if there are any problems, also feel free to hack/iterate on I see a strange behaviour when clocking in with C-c C-x C-i. Sometimes (!) there is no new CLOCK: entry created. The TODO state changes as expected, but no new CLOCK: line is created, even when clocking out. Looks like this happens when the initial TODO state is set. Maybe I missed a change in the behaviour? Rainer, I can't reproduce this, can you give me a few more details? 1. Are you doing C-c C-x C-i from agenda, or from an Org File? from org file 2. I don't understand the "TODO state changes as expected" part, I thought clock-in command has no effect on todo state, ie it simply adds CLOCK line to logbook drawer. Is there some extra configuration I need to change to enable this bit? I have set "org-clock-in-switch-to-state" to "INARBEIT" state in my state sequence #+SEQ_TODO: TODO INARBEIT WARTEN | MOVED DONE CANCELED DELEGATED As soon as I am in state "INARBEIT" and doing a clockin, the CLOCK: line appears. 3. Are sticky agendas enabled? YES! 4. If its from agenda, and its sticky, is it freshly generated, or was it refreshed with "g" or "r" key? it is not from agenda 5. If its from sticky agenda, can you reproduce it without enabling sticky agendas? Let me see: no, problem occurs with or without sticky agendas So far this looks to me as its unrelated to sticky changes, could you by any chance try commit 3bd1c2e9bff539c94f92f1ec919f8f0f1640f8c0 which is 1 before sticky merge , and see if same scenario is broken there? The git commands to do it (ignore if your git-fu is strong) git checkout 3bd1c2e9bff539c94f92f1ec919f8f0f1640f8c0 .. test .. git checkout master .. back to normal .. Regards, Max Hi Max, I just tested. The missing CLOCK: entry is unrelated to your merge. It also appears in 3bd1c2e9bff539c94f92f1ec919f8f0f1640f8c0 So this must be related to another change. Can anyone confirm? Sorry and thanks you for the work on the sticky agendas! Regards, Rainer
Re: [O] Sticky agenda branch merged
Hi Max, I'll try later. What I just found: being in a sticky agenda and trying "v r" I get this error which was not there before the merge: org-agenda-check-type: Not allowed in nil-type agenda buffers. Actually "v c" directly before entering "v r" gave results! Thanks, Rainer Am 17.04.2012 17:32, schrieb Max Mikhanosha: > Hi Rainer, > > At Tue, 17 Apr 2012 15:23:00 +0200, > Rainer Stengele wrote: >> >> Am 17.04.2012 14:29, schrieb Max Mikhanosha: >>> At Tue, 17 Apr 2012 12:09:40 +0200, >>> Rainer Stengele wrote: Am 16.04.2012 11:47, schrieb Max Mikhanosha: > I had just pushed a merge of max-sticky-agenda branch to master, let > me know if there are any problems, also feel free to hack/iterate on I see a strange behaviour when clocking in with C-c C-x C-i. Sometimes (!) there is no new CLOCK: entry created. The TODO state changes as expected, but no new CLOCK: line is created, even when clocking out. Looks like this happens when the initial TODO state is set. Maybe I missed a change in the behaviour? >>> Rainer, I can't reproduce this, can you give me a few more details? >>> >>> 1. Are you doing C-c C-x C-i from agenda, or from an Org File? >> >> from org file >> >>> >>> 2. I don't understand the "TODO state changes as expected" part, I >>> thought clock-in command has no effect on todo state, ie it simply >>> adds CLOCK line to logbook drawer. Is there some extra configuration I >>> need to change to enable this bit? >> >> I have set "org-clock-in-switch-to-state" to "INARBEIT" state in my state >> sequence >> >> #+SEQ_TODO: TODO INARBEIT WARTEN | MOVED DONE CANCELED DELEGATED >> >> As soon as I am in state "INARBEIT" and doing a clockin, the CLOCK: line >> appears. >>> >>> 3. Are sticky agendas enabled? >> >> YES! >>> >>> 4. If its from agenda, and its sticky, is it freshly generated, or was >>>it refreshed with "g" or "r" key? >> it is not from agenda >>> >>> 5. If its from sticky agenda, can you reproduce it without enabling sticky >>> agendas? >> Let me see: no, problem occurs with or without sticky agendas >>> > > So far this looks to me as its unrelated to sticky changes, could you > by any chance try commit 3bd1c2e9bff539c94f92f1ec919f8f0f1640f8c0 > which is 1 before sticky merge , and see if same scenario is broken > there? > > The git commands to do it (ignore if your git-fu is strong) > > git checkout 3bd1c2e9bff539c94f92f1ec919f8f0f1640f8c0 > ... test .. > git checkout master > ... back to normal .. > > Regards, > Max > > >
Re: [O] Sticky agenda branch merged
Hi Rainer, At Tue, 17 Apr 2012 15:23:00 +0200, Rainer Stengele wrote: > > Am 17.04.2012 14:29, schrieb Max Mikhanosha: > > At Tue, 17 Apr 2012 12:09:40 +0200, > > Rainer Stengele wrote: > >> Am 16.04.2012 11:47, schrieb Max Mikhanosha: > >>> I had just pushed a merge of max-sticky-agenda branch to master, let > >>> me know if there are any problems, also feel free to hack/iterate on > >> I see a strange behaviour when clocking in with C-c C-x C-i. > >> Sometimes (!) there is no new CLOCK: entry created. > >> The TODO state changes as expected, but no new CLOCK: line is created, > >> even when clocking out. > >> Looks like this happens when the initial TODO state is set. > >> > >> Maybe I missed a change in the behaviour? > > Rainer, I can't reproduce this, can you give me a few more details? > > > > 1. Are you doing C-c C-x C-i from agenda, or from an Org File? > > from org file > > > > > 2. I don't understand the "TODO state changes as expected" part, I > > thought clock-in command has no effect on todo state, ie it simply > > adds CLOCK line to logbook drawer. Is there some extra configuration I > > need to change to enable this bit? > > I have set "org-clock-in-switch-to-state" to "INARBEIT" state in my state > sequence > > #+SEQ_TODO: TODO INARBEIT WARTEN | MOVED DONE CANCELED DELEGATED > > As soon as I am in state "INARBEIT" and doing a clockin, the CLOCK: line > appears. > > > > 3. Are sticky agendas enabled? > > YES! > > > > 4. If its from agenda, and its sticky, is it freshly generated, or was > >it refreshed with "g" or "r" key? > it is not from agenda > > > > 5. If its from sticky agenda, can you reproduce it without enabling sticky > > agendas? > Let me see: no, problem occurs with or without sticky agendas > > So far this looks to me as its unrelated to sticky changes, could you by any chance try commit 3bd1c2e9bff539c94f92f1ec919f8f0f1640f8c0 which is 1 before sticky merge , and see if same scenario is broken there? The git commands to do it (ignore if your git-fu is strong) git checkout 3bd1c2e9bff539c94f92f1ec919f8f0f1640f8c0 .. test .. git checkout master .. back to normal .. Regards, Max
Re: [O] Sticky agenda branch merged
Hi Max, see below Am 17.04.2012 14:29, schrieb Max Mikhanosha: > At Tue, 17 Apr 2012 12:09:40 +0200, > Rainer Stengele wrote: >> Am 16.04.2012 11:47, schrieb Max Mikhanosha: >>> I had just pushed a merge of max-sticky-agenda branch to master, let >>> me know if there are any problems, also feel free to hack/iterate on >> I see a strange behaviour when clocking in with C-c C-x C-i. >> Sometimes (!) there is no new CLOCK: entry created. >> The TODO state changes as expected, but no new CLOCK: line is created, even >> when clocking out. >> Looks like this happens when the initial TODO state is set. >> >> Maybe I missed a change in the behaviour? > Rainer, I can't reproduce this, can you give me a few more details? > > 1. Are you doing C-c C-x C-i from agenda, or from an Org File? from org file > > 2. I don't understand the "TODO state changes as expected" part, I > thought clock-in command has no effect on todo state, ie it simply > adds CLOCK line to logbook drawer. Is there some extra configuration I > need to change to enable this bit? I have set "org-clock-in-switch-to-state" to "INARBEIT" state in my state sequence #+SEQ_TODO: TODO INARBEIT WARTEN | MOVED DONE CANCELED DELEGATED As soon as I am in state "INARBEIT" and doing a clockin, the CLOCK: line appears. > > 3. Are sticky agendas enabled? YES! > > 4. If its from agenda, and its sticky, is it freshly generated, or was >it refreshed with "g" or "r" key? it is not from agenda > > 5. If its from sticky agenda, can you reproduce it without enabling sticky > agendas? Let me see: no, problem occurs with or without sticky agendas > > Regards, > Max Thanks for checking! Regards, Rainer
Re: [O] Sticky agenda branch merged
At Tue, 17 Apr 2012 12:09:40 +0200, Rainer Stengele wrote: > > Am 16.04.2012 11:47, schrieb Max Mikhanosha: > > I had just pushed a merge of max-sticky-agenda branch to master, let > > me know if there are any problems, also feel free to hack/iterate on > > I see a strange behaviour when clocking in with C-c C-x C-i. > Sometimes (!) there is no new CLOCK: entry created. > The TODO state changes as expected, but no new CLOCK: line is created, even > when clocking out. > Looks like this happens when the initial TODO state is set. > > Maybe I missed a change in the behaviour? Rainer, I can't reproduce this, can you give me a few more details? 1. Are you doing C-c C-x C-i from agenda, or from an Org File? 2. I don't understand the "TODO state changes as expected" part, I thought clock-in command has no effect on todo state, ie it simply adds CLOCK line to logbook drawer. Is there some extra configuration I need to change to enable this bit? 3. Are sticky agendas enabled? 4. If its from agenda, and its sticky, is it freshly generated, or was it refreshed with "g" or "r" key? 5. If its from sticky agenda, can you reproduce it without enabling sticky agendas? Regards, Max
Re: [O] Sticky agenda branch merged
Am 16.04.2012 11:47, schrieb Max Mikhanosha: > I had just pushed a merge of max-sticky-agenda branch to master, let > me know if there are any problems, also feel free to hack/iterate on > it, if you have question as to why something was done, I'll do my best > to answer. > > In particular I just seen a new commit introducing filter on > categories, and org-agenda-filtered-by-top-category probably needs to > be included into local variable list to have it work per agenda > buffer. > > Also the individual calls to org-todo-list and such, do not work right > with sticky agenda as there is nothing to catch the 'exit tag, that is > thrown by `org-prepare-agenda' when it finds cached buffer. I'm not > sure there is more elegant way of fixing it, other then wrapping all > the individual scanner pieces with (catch) blocks, that re-throw if > they had detected that they been called from (org-agenda) command > > Regards, > Max > > Hi, I see a strange behaviour when clocking in with C-c C-x C-i. Sometimes (!) there is no new CLOCK: entry created. The TODO state changes as expected, but no new CLOCK: line is created, even when clocking out. Looks like this happens when the initial TODO state is set. Maybe I missed a change in the behaviour? Regards, Rainer
Re: [O] Sticky agenda branch merged
Max Mikhanosha writes: Hi Max, > I had pushed a fix, which should fix `org-agenda-to-appt' Yes, it seems to work again. Thanks a lot, Tassilo
Re: [O] Sticky agenda branch merged
Max Mikhanosha writes: > I had pushed a fix, which should fix `org-agenda-to-appt' Thanks, it worked. Charles -- "The world is beating a path to our door" -- Bruce Perens, (Open Sources, 1999 O'Reilly and Associates) pgpS9uKFsMF8D.pgp Description: PGP signature
Re: [O] Sticky agenda branch merged
At Mon, 16 Apr 2012 19:44:54 +0200,
Tassilo Horn wrote:
>
> > I had just pushed a merge of max-sticky-agenda branch to master, let
> > me know if there are any problems,...
>
> since the merge, I get an error on emacs startup. The error is caused
> by invoking `org-agenda-to-appt' on emacs startup.
>
> Here's a backtrace:
>
> --8<---cut here---start->8---
> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
> org-agenda-new-marker(9228)
> byte-code("\306 ... VBV)\311\207" [s txt pos save-match-data-internal
> todo-state org-agenda-repeating-timestamp-show-all org-agenda-skip
> match-string 1 nil match-data ((byte-code "\301\302\"\207"
> [save-match-data-internal set-match-data evaporate] 3)) org-get-todo-state t
> org-time-string-to-absolute past 0 abs functionp org-is-habit-p
> org-get-category get-text-property org-category-position re-search-backward
> "^\\*+[]+" throw :skip assoc org-get-tags-at
> buffer-substring-no-properties "^\n" string-match "
> \\([012]?[0-9]:[0-9][0-9]\\)" " " time org-agenda-format-item format
> org-scheduled-previously org-scheduled-today org-scheduled
> org-habit-parse-todo org-add-props undone-face face org-agenda-done
> org-marker org-agenda-new-marker org-hd-marker type "past-scheduled" ...] 26)
> org-agenda-get-scheduled(nil)
I had pushed a fix, which should fix `org-agenda-to-appt'
Regards,
Max
Re: [O] Sticky agenda branch merged
Tassilo Horn writes:
> since the merge, I get an error on emacs startup. The error is caused
> by invoking `org-agenda-to-appt' on emacs startup.
You beat me to it. I am seeing the same thing.
Also, I am able to run the function manually if there is an Agenda
buffer. Without an Agenda buffer being up, I get:
,[ Backtrace ]
| Debugger entered--Lisp error: (error "Selecting deleted buffer")
| org-agenda-new-marker(2614)
| byte-code("\306 \210\307\310!\311\310\224S\312 \313\216\314 *
\315=\206 \f\235<\316\307\310!=\317=Z?@\205??\320WA?\320W\203\\\321?!BW\203\\@\203\\C\203c?\320U\203\312\212\fD\235\211E\203\212F\204\205?\320U\203\205\322\323!\203\212\323
\203\212\311\202C\322\323!\205\222\323 G\324
H\325`\326\"I\327\330\311\315#\204\254J\202C\320\225b\210\320\224KG\203\320L\203\310@\204\362M\203\362\331\332\311\"\210\202\362N\315=\204\341N\203\362A\203\362\333KO\"\211P\203\362\331\332\311\"\210\334
Q\335`\336\311w\210`\"R\337\340\"\203\310\224\311O\341PS\202\342S\343?\320U\203$T@\202.\344TA@\310?Z\"RHQ?\320U\205=S\311G&
\203\311G\204UA\203U\345\202_@\203^\346\202_\347+G\205h\350 G\351
U\352+\353E\203{\354\202}+\355\356\n!\357\356K!\360A\203\220\361\202\221\362\363A\203\234>\202\2363\364G\203\253\365G!\202\265\366\367\370?Z\371
!#\372H\326I\373G\304\f&\210VBV)\311\207" [s txt pos
save-match-data-internal todo-state org-agenda-repeating-timestamp-show-all
org-agenda-skip match-string 1 nil match-data ((byte-code "\301\302\"\207"
[save-match-data-internal set-match-data evaporate] 3)) org-get-todo-state t
org-time-string-to-absolute past 0 abs functionp org-is-habit-p
org-get-category get-text-property org-category-position re-search-backward
"^\\*+[ ]+" throw :skip assoc org-get-tags-at
buffer-substring-no-properties "^\n" string-match "
\\([012]?[0-9]:[0-9][0-9]\\)" " " time org-agenda-format-item format
org-scheduled-previously org-scheduled-today org-scheduled org-habit-parse-todo
org-add-props undone-face face org-agenda-done org-marker org-agenda-new-marker
org-hd-marker type "past-scheduled" ...] 26)
| org-agenda-get-scheduled(nil)
| org-agenda-get-day-entries("~/Desktop/Projects/plans/AreasofFocus.org" (4
16 2012) :deadline :scheduled :timestamp)
| apply(org-agenda-get-day-entries
"~/Desktop/Projects/plans/AreasofFocus.org" (4 16 2012) (:deadline :scheduled
:timestamp))
| org-agenda-to-appt(nil)
| call-interactively(org-agenda-to-appt t nil)
| execute-extended-command(nil)
| call-interactively(execute-extended-command nil nil)
`
Charles
--
"Nature abhors a Vacuum"
-- Brian Behlendorf on OSS (Open Sources, 1999 O'Reilly and Associates)
pgpqK9LHBnVbS.pgp
Description: PGP signature
Re: [O] Sticky agenda branch merged
Max Mikhanosha writes:
Hi Max,
> I had just pushed a merge of max-sticky-agenda branch to master, let
> me know if there are any problems,...
since the merge, I get an error on emacs startup. The error is caused
by invoking `org-agenda-to-appt' on emacs startup.
Here's a backtrace:
--8<---cut here---start->8---
Debugger entered--Lisp error: (wrong-type-argument stringp nil)
org-agenda-new-marker(9228)
byte-code("\306 ... VBV)\311\207" [s txt pos save-match-data-internal
todo-state org-agenda-repeating-timestamp-show-all org-agenda-skip match-string
1 nil match-data ((byte-code "\301\302\"\207" [save-match-data-internal
set-match-data evaporate] 3)) org-get-todo-state t org-time-string-to-absolute
past 0 abs functionp org-is-habit-p org-get-category get-text-property
org-category-position re-search-backward "^\\*+[ ]+" throw :skip assoc
org-get-tags-at buffer-substring-no-properties "^\n" string-match "
\\([012]?[0-9]:[0-9][0-9]\\)" " " time org-agenda-format-item format
org-scheduled-previously org-scheduled-today org-scheduled org-habit-parse-todo
org-add-props undone-face face org-agenda-done org-marker org-agenda-new-marker
org-hd-marker type "past-scheduled" ...] 26)
org-agenda-get-scheduled(nil)
org-agenda-get-day-entries("/home/horn/Repos/org/remember.org" (4 16 2012)
:deadline :scheduled :timestamp)
apply(org-agenda-get-day-entries "/home/horn/Repos/org/remember.org" (4 16
2012) (:deadline :scheduled :timestamp))
org-agenda-to-appt(t)
th-org-agenda-to-appt()
eval-buffer(# nil "/home/horn/.emacs" nil t) ; Reading at
buffer position 50862
load-with-code-conversion("/home/horn/.emacs" "/home/horn/.emacs" t t)
load("~/.emacs" t t)
#[0 "\205 ... \211#)\262\207" [init-file-user system-type
delayed-warnings-list user-init-file inhibit-default-init
inhibit-startup-screen ms-dos "~" "/_emacs" windows-nt "/.emacs"
directory-files nil "^\\.emacs\\(\\.elc?\\)?$" "~/.emacs"
"^_emacs\\(\\.elc?\\)?$" (initialization "`_emacs' init file is deprecated,
please use `.emacs'") "~/_emacs" t load expand-file-name "init"
file-name-as-directory "/.emacs.d" file-name-extension "elc"
file-name-sans-extension ".el" file-exists-p file-newer-than-file-p message
"Warning: %s is newer than %s" sit-for 1 "default"] 7 "\n\n(fn)"]()
command-line()
normal-top-level()
--8<---cut here---end--->8---
Please let me know if you need any further details.
Bye,
Tassilo
[O] Sticky agenda branch merged
I had just pushed a merge of max-sticky-agenda branch to master, let me know if there are any problems, also feel free to hack/iterate on it, if you have question as to why something was done, I'll do my best to answer. In particular I just seen a new commit introducing filter on categories, and org-agenda-filtered-by-top-category probably needs to be included into local variable list to have it work per agenda buffer. Also the individual calls to org-todo-list and such, do not work right with sticky agenda as there is nothing to catch the 'exit tag, that is thrown by `org-prepare-agenda' when it finds cached buffer. I'm not sure there is more elegant way of fixing it, other then wrapping all the individual scanner pieces with (catch) blocks, that re-throw if they had detected that they been called from (org-agenda) command Regards, Max
