subject:"Org Agenda Error"

Re: Org Agenda Error

2022-06-13 Thread Bhavin Gandhi

On Sun, 12 Jun 2022 at 23:16, Bhavin Gandhi  wrote:
> 1. emacs -Q
> 2. Create test.org with following content
>
> * TODO Repeating entry
> SCHEDULED: <2022-05-01 Mon ++2d>
>
> 3. C-c C-t on the entry, shows the above error. And shifts the scheduled
>date correctly.

When this error appears, the log note entry about state change is not
added. I found this issue for the first time when I saw the state
change log notes were missing.

If I do C-c C-t again on the same entry, we get the note.
- State "DONE"   from "TODO"   [2022-06-13 Mon 22:48]

This is missing when we hit the error mentioned in the first mail.

Re: Org Agenda Error

2022-06-12 Thread Michael Powe


hello,

Thank you for the followup. Yes, I should have mentioned that the date 
is correctly updated following the error. Very odd, considering the text 
of the error message.


Thanks.

mp

On 6/12/2022 13:46, Bhavin Gandhi wrote:

Hello Michael

On Sun, 12 Jun 2022 at 21:20, Michael Powe  wrote:

[MP] Error in post-command-hook (org-add-log-note): (error "Can’t expand minibuffer 
to full frame")
[MP] 10 repeater intervals were not enough to shift date past today.  Continue? 
(y or n) y

I have been seeing these with my repeating tasks recently, and took this
bug report as an opportunity to see if I can reproduce it with emacs -Q.

1. emacs -Q
2. Create test.org with following content

* TODO Repeating entry
SCHEDULED: <2022-05-01 Mon ++2d>

3. C-c C-t on the entry, shows the above error. And shifts the scheduled
date correctly.

This happens on the Org mode version bundled with Emacs 28.1
i.e. release_9.5.2-25-gaf6f12.
And with latest main: release_9.5.4-544-gae168d

--
Bhavin Gandhi (bhavin192) | https://geeksocket.in


--
"Do not neglect to do good, and to share what you have." - Hebrews 13:16a
Michael Powe
Naugatuck CT USA
po...@ctpowe.net

Re: Org Agenda Error

2022-06-12 Thread Bhavin Gandhi

Hello Michael

On Sun, 12 Jun 2022 at 21:20, Michael Powe  wrote:
> [MP] Error in post-command-hook (org-add-log-note): (error "Can’t expand 
> minibuffer to full frame")
> [MP] 10 repeater intervals were not enough to shift date past today.  
> Continue? (y or n) y

I have been seeing these with my repeating tasks recently, and took this
bug report as an opportunity to see if I can reproduce it with emacs -Q.

1. emacs -Q
2. Create test.org with following content

* TODO Repeating entry
SCHEDULED: <2022-05-01 Mon ++2d>

3. C-c C-t on the entry, shows the above error. And shifts the scheduled
   date correctly.

This happens on the Org mode version bundled with Emacs 28.1
i.e. release_9.5.2-25-gaf6f12.
And with latest main: release_9.5.4-544-gae168d

--
Bhavin Gandhi (bhavin192) | https://geeksocket.in

Org Agenda Error

2022-06-12 Thread Michael Powe


Hello,

Not sure if this qualifies as a bug.

This occurred when discarding an agenda item that was more than 60 days 
overdue. (The repeater is 6 days.) I imagine most people take better 
care of their agenda. ;-)


TODO state changed to DISCARDED
TODO state changed to TODO
[MP] Error in post-command-hook (org-add-log-note): (error "Can’t expand 
minibuffer to full frame")
[MP] 10 repeater intervals were not enough to shift date past today.  
Continue? (y or n) y

Entry repeats: SCHEDULED: <2022-06-16 Thu ++6d>

The two items I initialed travel together. I got this message several times.

* Org mode version 9.5.4 (release_9.5.4-535-ged6f8d.dirty @ 
c:/Users/micha/AppData/Roaming/.emacs.d/org-new/org-mode/lisp/)


* GNU Emacs 29.0.50 (build 2, x86_64-w64-mingw32) of 2022-06-09

Thanks.

mp

--
"Do not neglect to do good, and to share what you have." - Hebrews 13:16a
Michael Powe
Naugatuck CT USA
po...@ctpowe.net

Re: [O] org-agenda error

2016-03-15 Thread Peter Salazar

Update: I fixed the org-agenda problem. Turns out the problem was that I'd
created my own custom defun called org-today, and it was interfering with
org-agenda.

The helm-org-in-buffer-headings error is still occurring. Thanks for any
thoughts.

On Tue, Mar 15, 2016 at 7:58 PM, Peter Salazar 
wrote:

> Unfortunately, that's not the case (that helm-org-in-buffer-headings) is
> called in a non-org buffer. It happens whenever I call it from within any
> org-file. I also tried calling it from within a short, minimal org-file
> with just a few headings of various levels, and I get the same error.
>
> The error, once again, is this:
> http://i.imgur.com/FoTiwoq.png
>
> And again, the error I get when I call org-agenda is this:
> http://pastebin.com/wCBgAQLp
>
>
> On Thu, Mar 10, 2016 at 3:21 AM, Nicolas Goaziou 
> wrote:
>
>> Hello,
>>
>> Peter Salazar  writes:
>>
>> > Any thoughts on that? I'm not sure if it's related, but I also get
>> errors
>> > when I try to call helm-org-in-buffer-headings. Somehow the backtrace
>> gets
>> > immediately erased, so here's a screenshot:
>> > http://i.imgur.com/FoTiwoq.png
>>
>> From the above, it looks like `helm-org--get-candidate-in-file' is
>> erroneously called from a non-Org buffer (here, "*Backtrace*").  Outside
>> Org, `org-complex-heading-regexp' is nil, hence the result.
>>
>> Regards,
>>
>> --
>> Nicolas Goaziou
>>
>
>

Re: [O] org-agenda error

2016-03-15 Thread Peter Salazar

Unfortunately, that's not the case (that helm-org-in-buffer-headings) is
called in a non-org buffer. It happens whenever I call it from within any
org-file. I also tried calling it from within a short, minimal org-file
with just a few headings of various levels, and I get the same error.

The error, once again, is this:
http://i.imgur.com/FoTiwoq.png

And again, the error I get when I call org-agenda is this:
http://pastebin.com/wCBgAQLp

On Thu, Mar 10, 2016 at 3:21 AM, Nicolas Goaziou 
wrote:

> Hello,
>
> Peter Salazar  writes:
>
> > Any thoughts on that? I'm not sure if it's related, but I also get errors
> > when I try to call helm-org-in-buffer-headings. Somehow the backtrace
> gets
> > immediately erased, so here's a screenshot:
> > http://i.imgur.com/FoTiwoq.png
>
> From the above, it looks like `helm-org--get-candidate-in-file' is
> erroneously called from a non-Org buffer (here, "*Backtrace*").  Outside
> Org, `org-complex-heading-regexp' is nil, hence the result.
>
> Regards,
>
> --
> Nicolas Goaziou
>

Re: [O] org-agenda error

2016-03-10 Thread Nicolas Goaziou

Hello,

Peter Salazar  writes:

> Any thoughts on that? I'm not sure if it's related, but I also get errors
> when I try to call helm-org-in-buffer-headings. Somehow the backtrace gets
> immediately erased, so here's a screenshot:
> http://i.imgur.com/FoTiwoq.png

>From the above, it looks like `helm-org--get-candidate-in-file' is
erroneously called from a non-Org buffer (here, "*Backtrace*").  Outside
Org, `org-complex-heading-regexp' is nil, hence the result.

Regards,

-- 
Nicolas Goaziou

Re: [O] org-agenda error

2016-03-09 Thread Peter Salazar

Any thoughts on that? I'm not sure if it's related, but I also get errors
when I try to call helm-org-in-buffer-headings. Somehow the backtrace gets
immediately erased, so here's a screenshot:
http://i.imgur.com/FoTiwoq.png

On Mon, Mar 7, 2016 at 10:40 AM, Peter Salazar 
wrote:

> Well that's interesting. When I do C-u M-x org-reload and then call
> org-agenda, it displays correctly with no error.
>
> How do I debug? I already went into my config files and commented out all
> the code containing the word org-agenda, but the error still happens.
>
>
> On Mon, Mar 7, 2016 at 6:09 AM, Nicolas Goaziou 
> wrote:
>
>> Hello,
>>
>> Peter Salazar  writes:
>>
>> > I'm suddenly getting "byte-code: Wrong type argument:
>> number-or-marker-p,
>> > nil" when I try to call org-agenda. This happens even when
>> org-agenda-files
>> > is set to nil. Here's the backtrace. Any thoughts on how I can track
>> down
>> > the source of the problem?
>>
>> Could you provide the backtrace running un-compiled Org? It is just
>> a matter of calling C-u M-x org-reload.
>>
>> Regards,
>>
>> --
>> Nicolas Goaziou
>>
>
>

Re: [O] org-agenda error

2016-03-07 Thread Peter Salazar

Well that's interesting. When I do C-u M-x org-reload and then call
org-agenda, it displays correctly with no error.

How do I debug? I already went into my config files and commented out all
the code containing the word org-agenda, but the error still happens.

On Mon, Mar 7, 2016 at 6:09 AM, Nicolas Goaziou 
wrote:

> Hello,
>
> Peter Salazar  writes:
>
> > I'm suddenly getting "byte-code: Wrong type argument: number-or-marker-p,
> > nil" when I try to call org-agenda. This happens even when
> org-agenda-files
> > is set to nil. Here's the backtrace. Any thoughts on how I can track down
> > the source of the problem?
>
> Could you provide the backtrace running un-compiled Org? It is just
> a matter of calling C-u M-x org-reload.
>
> Regards,
>
> --
> Nicolas Goaziou
>

Re: [O] org-agenda error

2016-03-07 Thread Nicolas Goaziou

Hello,

Peter Salazar  writes:

> I'm suddenly getting "byte-code: Wrong type argument: number-or-marker-p,
> nil" when I try to call org-agenda. This happens even when org-agenda-files
> is set to nil. Here's the backtrace. Any thoughts on how I can track down
> the source of the problem?

Could you provide the backtrace running un-compiled Org? It is just
a matter of calling C-u M-x org-reload.

Regards,

-- 
Nicolas Goaziou

[O] org-agenda error

2016-03-05 Thread Peter Salazar

Hey everyone,

I'm suddenly getting "byte-code: Wrong type argument: number-or-marker-p,
nil" when I try to call org-agenda. This happens even when org-agenda-files
is set to nil. Here's the backtrace. Any thoughts on how I can track down
the source of the problem?

Thanks!



Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
  calendar-gregorian-from-absolute(nil)
  byte-code("\206) \203(\n\203 ;\203\306\307\n
#\202%\n\203$\306\310\n\"\202%\311\206)\f\312\313!\210
\2064@\211;\203B\314\315\316\317
#!\320\321!\210\322\321!\210\323A\206WB\206WC!A\324 D
\206dDE\325AE\"\211F\326=\204{F\327=\205}GG\330\316\331\"\211HIG\203\224F\326W\203\231E\202\277\332\333E!!JGKJKZLEL\334W\203\271\326\202\272\334L\\Z+\211MCN\334OP?QRS\316\211TU\316\211VW\316\211XY\316\211LZ\316\211[\\\316\211]^\316_\335\336`D
\336ADa\257bFS\334cdcdW\203*N@TNBNcT\211c\202*N\237\211N@
]Ne\337e!@)\206B\334T^\340N@
fg\341g!fL*\210\342`fg\341g!fL*\210\343\323A!fg\341g!fL*\210h\204\362N@iNe\337e!@)j\344i!k\344j!l`Tm\203\262\345\346m!\316\347\350$\351\261\210\202\340\352A!\353jiZ\354W\203\333klU\203\321\306\355k\"\202\334\306\356kl#\202\334\357\360\261\210,\361T`S\347\350\362\317F#\210\363T!\210N\211AN\242\211L\203\374\333L!Y`TLDU\211\\\204
Z\204&LEU\203&`Z\2023Z\2033[\2043`[HI\316WI\211AI\242\211X\203N\364\365\215\210\202:n\203i\317o\366\367!\210\370Y!V\371WV\"W)W\204sp\203\362OTOq;\203\211\372q\373Y!\"\202\216qY!\351\261\210\374T`S\347\375Y!$\210\374T`S\362\317$\210\374T`S\376\317$\210\374T`S\377O$\210\\\203\310\374T`S\324\317$\210\201yWF\\#\211W\203\343\201zW\321\"\351\261\210\374T`S\201{L$\210\374T`S\377O$\210\202\362r\203U]\203U\330\316\331\"\346s!\316tu\201|u\201}\"u\201~u\201]#u\201~u\201\200^#u\201~u\201\201\321#u\201\202\201\203u\"\211tc\210+eb\210v\204b\201\204
\210\201\205e!\203r\201\205d!\204\237dSb\210\201\206\201\207!\210\201\205Z\206\211\201\210!\204\237Z\206\225\201\210b\210\201\206\201\210!\210Z\206\247\201\210b\210\361ed\201\211\321\201\212`
AE\201\213b\201\214w\257#\210S\201\215=\203\325\201\216 \210\201\217
\210\317x\201\220\357!.\207" [org-agenda-buffer-tmp-name
org-agenda-sticky org-keys org-match org-agenda-buffer-name start-day
format "*Org Agenda(%s:%s)*" "*Org Agenda(%s)*" "*Org Agenda(a)*"
org-agenda-prepare "Day/Week" time-to-days org-read-date nil t
org-compile-prefix-format agenda org-set-sorting-strategy
org-agenda-ndays-to-span org-today org-agenda-span-to-ndays 7 14
org-agenda-files ifmode calendar-day-of-week
calendar-gregorian-from-absolute 0 org-agenda-list quote last
org-starting-day make-local-variable org-arg-loc org-agenda-current-span
org-days-to-iso-week org-add-props copy-sequence face org-agenda-structure
"\n" org-agenda-span-name "-agenda" 350 " (W%02d)" " (W%02d-W%02d)" ""
":\n" add-text-properties ...] 12)
  org-agenda-list(nil)
  call-interactively(org-agenda-list)
  byte-code("\306 \307 \232\203\310\202\n \311\306\312\313 \"\"\314
\"p@\315\316
!A\306\211BC\306\211DE\306\211FGH\204`\317\320!\203K\204Q\321\322\323\306#\210\306IJ\306\211\223\210K\306\211\223\210\321\324\325\306#\210\321\324\326\306#\210pLM\204\202\327!\211G@MGANO\203\215\330\331M\"H\204\330N\203\330\321\322\323AC#\210N\332=\203\272pIJ\333
\306\223\210K\334
\306\223\210\202\330N\335=\203\330\212pI\336\337!\210J`\306\223\210K\340\337!\306\223\210)\341M
\"\211B\203\342B89\204\364\343\342B8!\203\342B8D\344\345B8!E\346B8FO\203#E;\203\330\347ME#\206\"\330\331M\"\321\324\325F#\210D\350=\2039\351F\352\"\202\237D\353=\203H\351F\354\"\202\237D\355=\203W\351F\356\"\202\237D\357=\203f\351F\360\"\202\237D\361=\203u\351F\362\"\202\237D\363=\203\204\351F\364\"\202\237D\365=\203\223\351F\366\"\202\237D\367=\203\242\351F\370\"\202\237D\371=\203\264\372
\210\351F\373\"\202\237D\374=\203\306\372
\210\351F\375\"\202\237D\376=\203\330\372
\210\351F\377\"\202\237\343D!\203\351\351F\201S\"\202\237\201TD!\203\374\351F\201U\"\202\237\201V\201WD\"\202\237\201XBA@
B\211AA\262\"\202\237M\201Y\232\203-\f\201Z\303!\202\237M\201[\232\203@\201\\\201]!\202\237M\201^\232\203S\201\\\201_!\202\237M\201`\232\203y\201_P\206g\201aPQPR\201\\Q!+\202\237M\201b\232\203\214\201\\\201c!\202\237M\201d\232\203\262\201cP\206\240\201ePQPR\201\\Q!+\202\237M\201f\232\203\305\201\\\201g!\202\237M\201h\232\203\353\201gP\206\331\201iPQPR\201\\Q!+\202\237M\201j\232\203\376\201\\\201k!\202\237M\201l\232\203\201g\306\201m\"\210\201n\201o\201p\337\211$\202\237M\201q\232\203_\201r\201s!\204:\201V\201t!\210N?\205\237\321\322\323AC#\210\201uPPQP

[Orgmode] Org-mode version 6.30trans (release_6.30d.856.ga70c); Search in agenda buffer for todo keyword gives org-agenda-error: Command not allowed in this line

2009-09-18 Thread Bernt Hansen

Everybody has a todo keyword of 'TODO' right?  :)

If you generate a list of tasks with C-c a t and then search for
'TODO' with c-s TODO and then repeat C-s until you're on a task with a
keyword of TODO and hit RET then navigation to display the task is
broken.

SPC and RET both return 'org-agenda-error: Command not allowed in this
line'

Searching for other keywords seems to break those but fix the tasks
for the previous match.

WORKAROUND: Hit 'g' in the agenda to redisplay and everything is
magically fixed.

-Bernt

Emacs  : GNU Emacs 22.2.1 (i486-pc-linux-gnu, GTK+ Version 2.12.11)
 of 2008-11-09 on raven, modified by Debian
Package: Org-mode version 6.30trans (release_6.30d.856.ga70c)

current state: (lots of stuff removed)
==
(setq
 org-todo-keyword-faces '((TODO :foreground red :weight bold)
  (STARTED :foreground blue :weight bold)
  (DONE :foreground forest green :weight bold)
  (WAITING :foreground orange :weight bold)
  (SOMEDAY :foreground magenta :weight bold)
  (CANCELLED :foreground forest green :weight bold)
  (QUOTE :foreground red :weight bold)
  (QUOTED :foreground magenta :weight bold)
  (APPROVED :foreground forest green :weight bold)
  (EXPIRED :foreground forest green :weight bold)
  (REJECTED :foreground forest green :weight bold)
  (OPEN :foreground blue :weight bold))
 org-agenda-custom-commands '((s Started Tasks todo STARTED
   ((org-agenda-todo-ignore-with-date nil)))
  (w Tasks waiting on something tags WAITING/!
   ((org-use-tag-inheritance nil)))
  (r Refile New Notes and Tasks tags 
LEVEL=1+REFILE
   ((org-agenda-todo-ignore-with-date nil)))
  (N Notes tags NOTE nil)
  (n Next tags NEXT-WAITING-CANCELLED/! nil)
  (p Projects tags-todo 
LEVEL=2/!-DONE-CANCELLED-WAITING nil))
 org-todo-state-tags-triggers '((CANCELLED (CANCELLED . t)) (WAITING 
(WAITING . t) (NEXT))
(SOMEDAY (WAITING . t)) (done (NEXT) 
(WAITING))
(TODO (WAITING) (CANCELLED))
(STARTED (WAITING) (NEXT . t)))
 org-todo-keywords '((sequence TODO(t!) STARTED(s!) | DONE(d!/!))
 (sequence WAITING(w@/!) SOMEDAY(S!) OPEN(O@) | 
CANCELLED(c@/!))
 (sequence QUOTE(q!) QUOTED(Q!) | APPROVED(A@) 
EXPIRED(E@)
  REJECTED(R@))
 )
 )


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [Orgmode] Org-mode version 6.30trans (release_6.30d.856.ga70c); Search in agenda buffer for todo keyword gives org-agenda-error: Command not allowed in this line

2009-09-18 Thread Carsten Dominik


Fixed, thanks.

- Carsten

On Sep 18, 2009, at 7:19 PM, Bernt Hansen wrote:


Everybody has a todo keyword of 'TODO' right?  :)

If you generate a list of tasks with C-c a t and then search for
'TODO' with c-s TODO and then repeat C-s until you're on a task with a
keyword of TODO and hit RET then navigation to display the task is
broken.

SPC and RET both return 'org-agenda-error: Command not allowed in this
line'

Searching for other keywords seems to break those but fix the tasks
for the previous match.

WORKAROUND: Hit 'g' in the agenda to redisplay and everything is
   magically fixed.

-Bernt

Emacs  : GNU Emacs 22.2.1 (i486-pc-linux-gnu, GTK+ Version 2.12.11)
of 2008-11-09 on raven, modified by Debian
Package: Org-mode version 6.30trans (release_6.30d.856.ga70c)

current state: (lots of stuff removed)
==
(setq
org-todo-keyword-faces '((TODO :foreground red :weight bold)
  (STARTED :foreground blue :weight bold)
  (DONE :foreground forest green :weight bold)
  (WAITING :foreground orange :weight bold)
  (SOMEDAY :foreground magenta :weight bold)
  (CANCELLED :foreground forest green :weight bold)
  (QUOTE :foreground red :weight bold)
  (QUOTED :foreground magenta :weight bold)
  (APPROVED :foreground forest green :weight bold)
  (EXPIRED :foreground forest green :weight bold)
  (REJECTED :foreground forest green :weight bold)
  (OPEN :foreground blue :weight bold))
org-agenda-custom-commands '((s Started Tasks todo STARTED
   ((org-agenda-todo-ignore-with-date nil)))
  (w Tasks waiting on something tags WAITING/!
   ((org-use-tag-inheritance nil)))
  (r Refile New Notes and Tasks tags 
LEVEL=1+REFILE
   ((org-agenda-todo-ignore-with-date nil)))
  (N Notes tags NOTE nil)
  (n Next tags NEXT-WAITING-CANCELLED/! nil)
			  (p Projects tags-todo LEVEL=2/!-DONE-CANCELLED- 
WAITING nil))
org-todo-state-tags-triggers '((CANCELLED (CANCELLED . t))  
(WAITING (WAITING . t) (NEXT))

(SOMEDAY (WAITING . t)) (done (NEXT) 
(WAITING))
(TODO (WAITING) (CANCELLED))
(STARTED (WAITING) (NEXT . t)))
org-todo-keywords '((sequence TODO(t!) STARTED(s!) |  
DONE(d!/!))
		 (sequence WAITING(w@/!) SOMEDAY(S!) OPEN(O@) |  
CANCELLED(c@/!))
		 (sequence QUOTE(q!) QUOTED(Q!) | APPROVED(A@)  
EXPIRED(E@)

  REJECTED(R@))
 )
)


___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode




___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Org Agenda Error

Re: Org Agenda Error

Re: Org Agenda Error

Org Agenda Error

Re: [O] org-agenda error

Re: [O] org-agenda error

Re: [O] org-agenda error

Re: [O] org-agenda error

Re: [O] org-agenda error

Re: [O] org-agenda error

[O] org-agenda error

[Orgmode] Org-mode version 6.30trans (release_6.30d.856.ga70c); Search in agenda buffer for todo keyword gives org-agenda-error: Command not allowed in this line

Re: [Orgmode] Org-mode version 6.30trans (release_6.30d.856.ga70c); Search in agenda buffer for todo keyword gives org-agenda-error: Command not allowed in this line

13 matches

Site Navigation

Mail list logo

Footer information