From: Marcelo de Moraes Serpa <celoserpa@gmail.com>
To: nicholas.dokos@hp.com
Cc: Bastien <bzg@altern.org>, Org Mode <emacs-orgmode@gnu.org>
Subject: Re: org-mode 7.01, error while scheduling item
Date: Wed, 18 Aug 2010 10:54:11 -0500 [thread overview]
Message-ID: <AANLkTinmiCC2Lmw=Q633Zk4N+RSoin1t0+W51LgYcT8C@mail.gmail.com> (raw)
In-Reply-To: <12008.1282069449@alphaville.usa.hp.com>
>(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)
>
>
>
next prev parent reply other threads:[~2010-08-18 15:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 20:35 org-mode 7.01, error while scheduling item Marcelo de Moraes Serpa
2010-07-23 5:44 ` David Maus
[not found] ` <AANLkTimsTbTCMhJAUbPpf3c-EEC3gNqs63JMoKGRcYyQ@mail.gmail.com>
2010-07-23 17:10 ` Marcelo de Moraes Serpa
2010-07-25 16:06 ` David Maus
2010-07-31 9:11 ` Bastien
2010-08-05 18:37 ` Marcelo de Moraes Serpa
2010-08-17 17:51 ` Marcelo de Moraes Serpa
2010-08-17 18:24 ` Nick Dokos
2010-08-18 15:54 ` Marcelo de Moraes Serpa [this message]
2010-08-18 19:57 ` Nick Dokos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTinmiCC2Lmw=Q633Zk4N+RSoin1t0+W51LgYcT8C@mail.gmail.com' \
--to=celoserpa@gmail.com \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).