org-mode 7.01, error while scheduling item

org-mode 7.01, error while scheduling item

[Marcelo de Moraes Serpa]

Hey guys,

I updated to org-mode Org-mode version 7.01trans
(release_7.01g.20.gdd484), and when trying to schedule an item with
C-c s, I get the following error:

org-eval-in-calendar: Wrong type argument: window-live-p, nil

Any ideas?

Thanks,

Marcelo.

Re: org-mode 7.01, error while scheduling item

[David Maus]

[-- Attachment #1.1: Type: text/plain, Size: 500 bytes --]

Marcelo de Moraes Serpa wrote:
>I updated to org-mode Org-mode version 7.01trans
>(release_7.01g.20.gdd484), and when trying to schedule an item with
>C-c s, I get the following error:

>org-eval-in-calendar: Wrong type argument: window-live-p, nil

>Any ideas?

Can you provide a backtrace for this error?

M-x toggle-debug-on-error RET

and hit the bug.

And which Emacs version do you use?

Best,
  -- David
--
OpenPGP... 0x99ADB83B5A4478E6
Jabber.... dmjena@jabber.org
Email..... dmaus@ictsoc.de

[-- Attachment #1.2: Type: application/pgp-signature, Size: 230 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

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

org-mode 7.01, error while scheduling item

[Marcelo de Moraes Serpa]

[-- Attachment #1: Type: text/plain, Size: 933 bytes --]

From: Marcelo de Moraes Serpa <celoserpa@gmail.com>
Date: 2010/7/23
Subject: Re: [Orgmode] org-mode 7.01, error while scheduling item
To: David Maus <dmaus@ictsoc.de>


GNU Emacs 23.2.1 (x86_64-apple-darwin, NS apple-appkit-1038.29) of 2010-05-08.

Backtrace attached.

Thanks,

Marcelo.

On Fri, Jul 23, 2010 at 12:44 AM, David Maus <dmaus@ictsoc.de> wrote:
> Marcelo de Moraes Serpa wrote:
>>I updated to org-mode Org-mode version 7.01trans
>>(release_7.01g.20.gdd484), and when trying to schedule an item with
>>C-c s, I get the following error:
>
>>org-eval-in-calendar: Wrong type argument: window-live-p, nil
>
>>Any ideas?
>
> Can you provide a backtrace for this error?
>
> M-x toggle-debug-on-error RET
>
> and hit the bug.
>
> And which Emacs version do you use?
>
> Best,
>  -- David
> --
> OpenPGP... 0x99ADB83B5A4478E6
> Jabber.... dmjena@jabber.org
> Email..... dmaus@ictsoc.de
>

[-- Attachment #2: backtrace.txt --]
[-- Type: text/plain, Size: 4223 bytes --]

Debugger entered--Lisp error: (wrong-type-argument window-live-p nil)
  select-window(nil)
  org-eval-in-calendar(nil t)
  byte-code("\306 \210\307\310\b!\311 \211\x19\211\x19AA@)\312\x1a\211^[\313U\203 \0\314\315!\202t\x01\v\313V\203\235\0\vS\x12	\211\x19\211\x19@)\x1c	\211\x19A@)\x1d	\211\x19AA@)^[\r\fS\316_\\\x1e@\f\317V\203\206\0\x0e@\f\320_\321\\\322\245Z\x16@\v\211^[\313W\203g\0\323\v!S\x13\324\v\320\246!\205}\0\324\v\325\246!?\206}\0\324\v\326\246!)\203\206\0\x0e@T\x16@\x0e@-\n\327_\\\n\320\245\\\n\325\245[\\\n\326\245\\\202t\x01\323\vT!\x12	\211\x19\211\x19@)\x1c	\211\x19A@)\x1d	\211\x19AA@)^[\r\fS\316_\\\x1e@\f\317V\203\377\0\x0e@\f\320_\321\\\322\245Z\x16@\v\211^[\313W\203\340\0\323\v!S\x13\324\v\320\246!\205\366\0\324\v\325\246!?\206\366\0\324\v\326\246!)\203\377\0\x0e@T\x16@\x0e@-\n\327_Z\n\320\245Z\n\325\245[Z\n\326\245Z\330\211\x19\211\x19@)\x1c	\211\x19A@)\x1d	\211\x19AA@)^[\r\fS\316_\\\x1e@\f\317V\203p\x01\x0e@\f\320_\321\\\322\245Z\x16@\v\211^[\313W\203Q\x01\323\v!S\x13\324\v\320\246!\205g\x01\324\v\325\246!?\206g\x01\324\v\326\246!)\203p\x01\x0e@T\x16@\x0e@-Z+Z!\210\331\312\332\"\210\333 \x1eA\334\x0eB!\x1eC\334\x0eD!\x1eD\335\x0eC\336\337#\210\335\x0eC\340\341#\210\335\x0eC\342\341#\210\335\x0eD\343\344#\210\335\x0eD\345\346#\210\335\x0eD\347\350#\210\335\x0eD\351\352#\210\335\x0eD\353\354#\210\335\x0eD\355\356#\210\335\x0eD\357\360#\210\335\x0eD\361\362#\210\335\x0eD\363\364#\210\335\x0eD\365\366#\210\335\x0eD\367\370#\210\335\x0eD\371\372#\210\335\x0eD\373\374#\210\335\x0eD\375\376#\210\335\x0eD\377\201K\0#\210\335\x0eD\201L\0\201M\0#\210\201N\0\201O\0!\210\201P\0\216\201Q\0\x0eC!\210\201R\0\201S\0\201T\0\"\210\201U\0\x0eE\x0eF\201V\0\312$\211\x16G\201W\0\x0eH\206O\x02\x0eIQ\x16J,\312\207" [def date offset-years year month day calendar calendar-forward-day time-to-days calendar-current-date nil 0 error "There was no year zero" 31 2 4 23 10 abs zerop 100 400 365 (12 31 -1) org-eval-in-calendar t current-local-map copy-keymap org-defkey "\r" org-calendar-select [mouse-1] org-calendar-select-mouse [mouse-2] [(meta shift left)] #[nil "\300\301!\207" [org-eval-in-calendar ...] 2 nil nil] [(meta shift right)] #[nil "\300\301!\207" [org-eval-in-calendar ...] 2 nil nil] [(meta shift up)] #[nil "\300\301!\207" [org-eval-in-calendar ...] 2 nil nil] [(meta shift down)] #[nil "\300\301!\207" [org-eval-in-calendar ...] 2 nil nil] [27 (shift left)] #[nil "\300\301!\207" [org-eval-in-calendar ...] 2 nil nil] [27 (shift right)] #[nil "\300\301!\207" [org-eval-in-calendar ...] 2 nil nil] [27 (shift up)] #[nil "\300\301!\207" [org-eval-in-calendar ...] 2 nil nil] [27 (shift down)] ...] 9)
  org-read-date(nil to-time nil nil nil nil)
  byte-code("\b\204>\0	\306>\203>\0\212\307\310!\210\212\311 \210`)\x12\312	\313=\203!\0\v\202\"\0\f\n\310#\203=\0\314\315!\x15\316\317\320\r!\"\x16.\r\205;\0\321\r!\x16/)	\203R\0\b\206Q\0\322\323\324\323\211\x0e.\x0e/&\x06\x10\x0e0\203}\0	\325\235\203}\0	\313=\203h\0\x0e1\202j\0\x0e2\326\261\x02\210\327\b\x0e3\323\211\211\x0e4C&\x06\210\323\x11\212\214\323\211\211\211\211\x1e5\x1d\x1e6\x1e7\x1e8\307\310!\210\330\x0e9\331P!\210\315\225b\210i\x168\332\225b\210m\203\255\0\333c\210\202\260\0\315u\210	\204\302\0\330\334\x0e:P!\204\302\0\335\336\323\"\210\330\x0e9!\204\345\0\330\337\x0e;\340Q!\203\345\0\314\315!\x0e<\232\204\345\0\332\224\332\225}\210\202\372\0\341\333!\210\342u\210``}\210\x0e=\203\372\0\343\x0e8!\210	\x0e>B\x167\x0e7\203^\x01\x0e7\211A\x167@\x166eb\210\x0e6\313=\203 \x01\312\v\323\310#\204?\x01\x0e6\344=\203/\x01\312\f\323\310#\204?\x01\x0e6\345=\203\0\x01\312\x0e?\323\310#\203\0\x01\346\347!\210\330\350!\203M\x01\346\347!\210\326\323x\210\330\351!\203\0\x01\346\347!\210\202\0\x01db\210\x0e=\203o\x01n\203o\x01\343\x0e8!\210	\203\303\x01n\204\203\x01`Sf\352=\204\203\x01\326\202\204\x01\347	\313=\203\217\x01\x0e1\202\242\x01	\344=\203\232\x01\x0e2\202\242\x01	\345=\205\242\x01\x0e@\326\261\x03\210\327\b\x0e3\206\265\x01	\345=\205\265\x01\x0eA	\345=\323\211\x0e4C&\x06\x15\315\x7f\210eb\210~\210\330\353!\203\334\x01`Sf\354\232\203\334\x01`S\355 |\210\r.\a\207" [time what end org-scheduled-time-regexp org-deadline-time-regexp ts (scheduled deadline) org-back-to-heading t outline-next-heading re-search-forward scheduled match-string 1 apply encode-time org-parse-time-string org-get-compact-tod org-read-date nil to-time (scheduled deadline) " " org-insert-time-stamp looking-at "\\( *\\)[^\r\n]*" 0 "\n" "[ 	]*" throw exit "[^\r\n]*?" "[^\r\n]*" insert-before-markers -1 org-indent-to-column deadline closed replace-match "" "--+<[^>]+>" " +" 32 "[ 	]*\n" 10 point-at-eol default-time default-input org-insert-labeled-timestamps-at-point org-scheduled-string ...] 7)
  org-add-planning-info(scheduled nil closed)
  org-schedule(nil)
  call-interactively(org-schedule nil nil)

[-- Attachment #3: Type: text/plain, Size: 201 bytes --]

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

Re: org-mode 7.01, error while scheduling item

[David Maus]

[-- Attachment #1.1: Type: text/plain, Size: 1011 bytes --]

Marcelo de Moraes Serpa wrote:
>GNU Emacs 23.2.1 (x86_64-apple-darwin, NS apple-appkit-1038.29) of 2010-05-08.

>Backtrace attached.

Thanks.  It looks like a problem with calendar.el: Org tries to use a
function in the calendar-buffer named "*Calendar*" and fails because
there is no window that contains such a buffer.

 - are there any customizations starting with "calendar-" in place?

 - can you open the calendar using M-x calendar RET?

 - if you can open the calendar, what is the name of the calendar
   buffer?

   To find out the name of the calendar buffer use this simple
   function:

   (defun dmj/print-buffer-name ()
     "Print name of current buffer."
     (interactive)
     (print (buffer-name)))

   Simply place cursor after this expression and evaluate it (C-x
   C-e).  After this you can M-x dmj/print-buffer-name RET to display
   the (internal) name of the calendar buffer.

Best,
  -- David

--
OpenPGP... 0x99ADB83B5A4478E6
Jabber.... dmjena@jabber.org
Email..... dmaus@ictsoc.de

[-- Attachment #1.2: Type: application/pgp-signature, Size: 230 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

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

Re: org-mode 7.01, error while scheduling item

[Bastien]

Hi Marcelo,

Marcelo de Moraes Serpa <celoserpa@gmail.com> writes:

> I updated to org-mode Org-mode version 7.01trans
> (release_7.01g.20.gdd484), and when trying to schedule an item with
> C-c s, I get the following error:
>
> org-eval-in-calendar: Wrong type argument: window-live-p, nil

Do you still have this error? 
Can you send a backtrace?

If you don't know how to produce a backtrace, please read this:

  http://orgmode.org/manual/Feedback.html

-- 
 Bastien

Re: org-mode 7.01, error while scheduling item

[Marcelo de Moraes Serpa]

Hi Bastien, I've posted the backtrace, it should be in the thread, a
few messages earlier.

Thanks,

Marcelo.

On Sat, Jul 31, 2010 at 4:11 AM, Bastien <bzg@altern.org> wrote:
> Hi Marcelo,
>
> Marcelo de Moraes Serpa <celoserpa@gmail.com> writes:
>
>> I updated to org-mode Org-mode version 7.01trans
>> (release_7.01g.20.gdd484), and when trying to schedule an item with
>> C-c s, I get the following error:
>>
>> org-eval-in-calendar: Wrong type argument: window-live-p, nil
>
> Do you still have this error?
> Can you send a backtrace?
>
> If you don't know how to produce a backtrace, please read this:
>
>  http://orgmode.org/manual/Feedback.html
>
> --
>  Bastien
>

Re: org-mode 7.01, error while scheduling item

[Marcelo de Moraes Serpa]

Hey guys, I'm still having this issue. I've tried downloading emacs
again from emacsformacosx.com, but the problem is still there.

Any ideas?

Thanks,

Marcelo.

On Thu, Aug 5, 2010 at 1:37 PM, Marcelo de Moraes Serpa
<celoserpa@gmail.com> wrote:
> Hi Bastien, I've posted the backtrace, it should be in the thread, a
> few messages earlier.
>
> Thanks,
>
> Marcelo.
>
> On Sat, Jul 31, 2010 at 4:11 AM, Bastien <bzg@altern.org> wrote:
>> Hi Marcelo,
>>
>> Marcelo de Moraes Serpa <celoserpa@gmail.com> writes:
>>
>>> I updated to org-mode Org-mode version 7.01trans
>>> (release_7.01g.20.gdd484), and when trying to schedule an item with
>>> C-c s, I get the following error:
>>>
>>> org-eval-in-calendar: Wrong type argument: window-live-p, nil
>>
>> Do you still have this error?
>> Can you send a backtrace?
>>
>> If you don't know how to produce a backtrace, please read this:
>>
>>  http://orgmode.org/manual/Feedback.html
>>
>> --
>>  Bastien
>>
>

Re: org-mode 7.01, error while scheduling item

[Nick Dokos]

Marcelo de Moraes Serpa <celoserpa@gmail.com> wrote:

> Hey guys, I'm still having this issue. I've tried downloading emacs
> again from emacsformacosx.com, but the problem is still there.
> 
> Any ideas?
> 
> Thanks,
> 
> Marcelo.
> 
> On Thu, Aug 5, 2010 at 1:37 PM, Marcelo de Moraes Serpa
> <celoserpa@gmail.com> wrote:
> > Hi Bastien, I've posted the backtrace, it should be in the thread, a
> > few messages earlier.
> >

I didn't find the backtrace in gmane, but I did find it eventually in
the list archive (I guess something thought it might be spam/malware and
got rid of it?) I append it (shortened to get rid of most of the binary
crud) to this mail for reference (it would be better if you reloaded the
appropriate .el files - org.el in this case - and *then* took the
backtrace.)

There are two select-window calls in org-eval-in-calendar: which one
fails?  I presume the first one, but it might be a good idea to make
sure.  Another way to ask the same thing: is there a *Calendar* buffer
popped up when you get the error? If not, why not?

Can you edebug-defun the function org-eval-in-calendar and then step
through it?

More questions than answers, but maybe something will click.

Nick


Function:
(defun org-eval-in-calendar (form &optional keepdate)
  "Eval FORM in the calendar window and return to current window.
Also, store the cursor date in variable org-ans2."
  (let ((sf (selected-frame))
	(sw (selected-window)))
    (select-window (get-buffer-window "*Calendar*" t))
    (eval form)
    (when (and (not keepdate) (calendar-cursor-to-date))
      (let* ((date (calendar-cursor-to-date))
	     (time (encode-time 0 0 0 (nth 1 date) (nth 0 date) (nth 2 date))))
	(setq org-ans2 (format-time-string "%Y-%m-%d" time))))
    (move-overlay org-date-ovl (1- (point)) (1+ (point)) (current-buffer))
    (select-window sw)
    (org-select-frame-set-input-focus sf)))

Backtrace:

Debugger entered--Lisp error: (wrong-type-argument window-live-p nil)
  select-window(nil)
  org-eval-in-calendar(nil t)
  byte-code(... [def date offset-years year month day calendar calendar-forward-day time-to-days calendar-current-date nil 0 error "There was no year zero" 31 2 4 23 10 abs zerop 100 400 365 (12 31 -1) org-eval-in-calendar t current-local-map copy-keymap org-defkey "
" org-calendar-select [mouse-1] org-calendar-select-mouse [mouse-2] [(meta shift left)] #[nil "\300\301!\207" [org-eval-in-calendar ...] 2 nil nil] [(meta shift right)] #[nil "\300\301!\207" [org-eval-in-calendar ...] 2 nil nil] [(meta shift up)] #[nil "\300\301!\207" [org-eval-in-calendar ...] 2 nil nil] [(meta shift down)] #[nil "\300\301!\207" [org-eval-in-calendar ...] 2 nil nil] [27 (shift left)] #[nil "\300\301!\207" [org-eval-in-calendar ...] 2 nil nil] [27 (shift right)] #[nil "\300\301!\207" [org-eval-in-calendar ...] 2 nil nil] [27 (shift up)] #[nil "\300\301!\207" [org-eval-in-calendar ...] 2 nil nil] [27 (shift down)] ...] 9)
  org-read-date(nil to-time nil nil nil nil)
  byte-code(... [time what end org-scheduled-time-regexp org-deadline-time-regexp ts (scheduled deadline) org-back-to-heading t outline-next-heading re-search-forward scheduled match-string 1 apply encode-time org-parse-time-string org-get-compact-tod org-read-date nil to-time (scheduled deadline) " " org-insert-time-stamp looking-at "\\( *\\)[^
\n]*" 0 "\n" "[ 	]*" throw exit "[^
\n]*?" "[^
\n]*" insert-before-markers -1 org-indent-to-column deadline closed replace-match "" "--+<[^>]+>" " +" 32 "[ 	]*\n" 10 point-at-eol default-time default-input org-insert-labeled-timestamps-at-point org-scheduled-string ...] 7)
  org-add-planning-info(scheduled nil closed)
  org-schedule(nil)
  call-interactively(org-schedule nil nil)

Re: org-mode 7.01, error while scheduling item

[Marcelo de Moraes Serpa]

>(it would be better if you reloaded the
>appropriate .el files - org.el in this case - and *then* took the
>backtrace.)

I am not an elisp expert, nor know the internals of orgmode, so sorry
about that.

>There are two select-window calls in org-eval-in-calendar: which one
>fails?  I presume the first one, but it might be a good idea to make
>sure.  Another way to ask the same thing: is there a *Calendar* buffer
>popped up when you get the error? If not, why not?

No calendar window pops up. I have no idea why.



On Tue, Aug 17, 2010 at 1:24 PM, Nick Dokos <nicholas.dokos@hp.com> wrote:
> Marcelo de Moraes Serpa <celoserpa@gmail.com> wrote:
>
>> Hey guys, I'm still having this issue. I've tried downloading emacs
>> again from emacsformacosx.com, but the problem is still there.
>>
>> Any ideas?
>>
>> Thanks,
>>
>> Marcelo.
>>
>> On Thu, Aug 5, 2010 at 1:37 PM, Marcelo de Moraes Serpa
>> <celoserpa@gmail.com> wrote:
>> > Hi Bastien, I've posted the backtrace, it should be in the thread, a
>> > few messages earlier.
>> >
>
> I didn't find the backtrace in gmane, but I did find it eventually in
> the list archive (I guess something thought it might be spam/malware and
> got rid of it?) I append it (shortened to get rid of most of the binary
> crud) to this mail for reference (it would be better if you reloaded the
> appropriate .el files - org.el in this case - and *then* took the
> backtrace.)
>
> There are two select-window calls in org-eval-in-calendar: which one
> fails?  I presume the first one, but it might be a good idea to make
> sure.  Another way to ask the same thing: is there a *Calendar* buffer
> popped up when you get the error? If not, why not?
>
> Can you edebug-defun the function org-eval-in-calendar and then step
> through it?
>
> More questions than answers, but maybe something will click.
>
> Nick
>
>
> Function:
> (defun org-eval-in-calendar (form &optional keepdate)
>  "Eval FORM in the calendar window and return to current window.
> Also, store the cursor date in variable org-ans2."
>  (let ((sf (selected-frame))
>        (sw (selected-window)))
>    (select-window (get-buffer-window "*Calendar*" t))
>    (eval form)
>    (when (and (not keepdate) (calendar-cursor-to-date))
>      (let* ((date (calendar-cursor-to-date))
>             (time (encode-time 0 0 0 (nth 1 date) (nth 0 date) (nth 2 date))))
>        (setq org-ans2 (format-time-string "%Y-%m-%d" time))))
>    (move-overlay org-date-ovl (1- (point)) (1+ (point)) (current-buffer))
>    (select-window sw)
>    (org-select-frame-set-input-focus sf)))
>
> Backtrace:
>
> Debugger entered--Lisp error: (wrong-type-argument window-live-p nil)
>  select-window(nil)
>  org-eval-in-calendar(nil t)
>  byte-code(... [def date offset-years year month day calendar calendar-forward-day time-to-days calendar-current-date nil 0 error "There was no year zero" 31 2 4 23 10 abs zerop 100 400 365 (12 31 -1) org-eval-in-calendar t current-local-map copy-keymap org-defkey "
> " org-calendar-select [mouse-1] org-calendar-select-mouse [mouse-2] [(meta shift left)] #[nil "\300\301!\207" [org-eval-in-calendar ...] 2 nil nil] [(meta shift right)] #[nil "\300\301!\207" [org-eval-in-calendar ...] 2 nil nil] [(meta shift up)] #[nil "\300\301!\207" [org-eval-in-calendar ...] 2 nil nil] [(meta shift down)] #[nil "\300\301!\207" [org-eval-in-calendar ...] 2 nil nil] [27 (shift left)] #[nil "\300\301!\207" [org-eval-in-calendar ...] 2 nil nil] [27 (shift right)] #[nil "\300\301!\207" [org-eval-in-calendar ...] 2 nil nil] [27 (shift up)] #[nil "\300\301!\207" [org-eval-in-calendar ...] 2 nil nil] [27 (shift down)] ...] 9)
>  org-read-date(nil to-time nil nil nil nil)
>  byte-code(... [time what end org-scheduled-time-regexp org-deadline-time-regexp ts (scheduled deadline) org-back-to-heading t outline-next-heading re-search-forward scheduled match-string 1 apply encode-time org-parse-time-string org-get-compact-tod org-read-date nil to-time (scheduled deadline) " " org-insert-time-stamp looking-at "\\( *\\)[^
> \n]*" 0 "\n" "[         ]*" throw exit "[^
> \n]*?" "[^
> \n]*" insert-before-markers -1 org-indent-to-column deadline closed replace-match "" "--+<[^>]+>" " +" 32 "[    ]*\n" 10 point-at-eol default-time default-input org-insert-labeled-timestamps-at-point org-scheduled-string ...] 7)
>  org-add-planning-info(scheduled nil closed)
>  org-schedule(nil)
>  call-interactively(org-schedule nil nil)
>
>
>

Re: org-mode 7.01, error while scheduling item

[Nick Dokos]

Marcelo de Moraes Serpa <celoserpa@gmail.com> wrote:

> >(it would be better if you reloaded the
> >appropriate .el files - org.el in this case - and *then* took the
> >backtrace.)
> 
> I am not an elisp expert, nor know the internals of orgmode, so sorry
> about that.
> 

No apology needed: it was meant as a (useful?) pointer for the future.
You might try it now just to see what happens:

M-x load-library <RET> org.el <RET>
M-x set-variable <RET> debug-on-error <RET> t <RET>

Then trigger the error and look at the backtrace. Then you can reload
the compiled version if you want:

M-x load-library <RET> org <RET>


> >There are two select-window calls in org-eval-in-calendar: which one
> >fails?  I presume the first one, but it might be a good idea to make
> >sure.  Another way to ask the same thing: is there a *Calendar* buffer
> >popped up when you get the error? If not, why not?
> 
> No calendar window pops up. I have no idea why.
> 

So the problem is that org-read-date which is supposed to pop up the
calendar, for some reason does not do so. What happens if you try to
pop up a calendar by hand?

M-x calendar <RET>

Nick