From: Douglas <zaphod4007@aol.com>
To: emacs-orgmode@gnu.org
Subject: Re: bulk org-agenda-do-date-later problem OMG BACKTRACE ATTACHED
Date: Sun, 05 Jan 2014 23:40:53 -0800 [thread overview]
Message-ID: <52CA5E05.6010902@aol.com> (raw)
In-Reply-To: <87a9f94vb4.fsf@gmail.com>
That worked. Thanks for explaining that. 1 pushed the entry one day
forward, or to today if the entry was prior to yesterday. I followed
the directions in Feedback, so I believe the backtrace was from
uncompiled code. I don't know why it wasn't sending.
Douglas
On 1/5/14 7:56 PM, Nick Dokos wrote:
> Douglas <zaphod4007@aol.com> writes:
>
>> The backtrace is attached. I am trying to bulk push org-agenda entries one day later in the agenda using org-agenda-do-date-later. I'm trying to change the timestamp of these
>> tasks. I am not using "SCHEDULED: [timestamp]". .emacs has not been included due to an abundance of personal information. org-agenda-files has been excised due to personal
>> information.
>>
>> What I did:
>>
>> 1. Loaded the org-agenda using "C-c a a".
>> 2. Set the view to day using "d".
>> 3. Went to the day before yesterday (Jan 3, 2014) at the time (Jan 5, 2014) using "b".
>> 4. Marked a done task (to test) for bulk action using "m".
>> 5. Brought up the menu for bulk action using "B".
>> 6. Selected the Function option using "f".
>> 7. Typed "org-agenda-do-date-later" into the echo/evaluation buffer at the bottom of the window and hit return.
>>
>> I expected the marked task to be pushed one day later in the agenda to January 4, 2014. I expected what normally occurs when I press S-<right>. Instead a long error popped up in
>> the echo buffer. Nothing happened in the agenda buffer. The mark remained.
>>
> The probable reason the backtrace did not make it through the mail is
> that it was produced using compiled code and so it contained binary
> stuff (perhaps nul bytes) that confused the mailer. You should try to
> produce backtraces using uncompiled code: they are much more informative
> in general. Or you could elide the strings containing the binary stuff
> as I have done below but that's less informative.
>
> In this case, the backtrace is simple enough:
>
> ,----
> | Debugger entered--Lisp error: (wrong-number-of-arguments #[(arg)
> | "..." [arg last-command this-command (16) (org-agenda-date-later-minutes org-agenda-date-earlier-minutes) org-agenda-date-later-minutes 1 (4) (org-agenda-date-later-hours org-agenda-date-earlier-hours) org-agenda-date-later-hours org-agenda-date-later prefix-numeric-value] 4 nil "P"] 0)
> | org-agenda-do-date-later() <<< called with no argument
> | eval((org-agenda-do-date-later))
> | ...
> | org-agenda-bulk-action(nil)
> | call-interactively(org-agenda-bulk-action nil nil)
> `----
>
> C-h f org-agenda-do-date-later RET says:
>
> ,----
> | org-agenda-do-date-later is an interactive Lisp function in
> | `org-agenda.el'.
> |
> | (org-agenda-do-date-later ARG)
> |
> | Not documented.
> `----
> ^^^
>
> i.e. org-agenda-do-date-later takes a mandatory argument while you
> called it with no argument. That's an error on your part, not a bug in
> the code. Try defining a helper function to do the appropriate
> impedance matching:
>
> (defun my-org-agend-do-one-day-later ()
> (interactive)
> (org-agenda-do-date-later 1))
>
> and passing that as the function in the bulk action.
>
> Untested and I'm not sure that 1 is the right value to pass.
>
next prev parent reply other threads:[~2014-01-06 7:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 1:25 bulk org-agenda-do-date-later problem OMG BACKTRACE ATTACHED Douglas
2014-01-06 3:56 ` Nick Dokos
2014-01-06 7:40 ` Douglas [this message]
2014-01-06 12:13 ` Nick Dokos
2014-01-06 18:11 ` Achim Gratz
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=52CA5E05.6010902@aol.com \
--to=zaphod4007@aol.com \
--cc=emacs-orgmode@gnu.org \
/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).