From: Michael Hoffman <gmane4-hoffman@sneakemail.com>
To: emacs-orgmode@gnu.org
Subject: Bulk re-scheduling in agenda view
Date: Sun, 11 Feb 2018 22:02:55 -0500 [thread overview]
Message-ID: <p5r011$gl9$1@blaine.gmane.org> (raw)
I am bulk re-scheduling items in an agenda view. I would like all the
selected items to be re-scheduled to a year later from their current
scheduled date. The org manual
<https://orgmode.org/manual/Agenda-commands.html> seems to indicate this
is possible using double plus:
> Schedule all items to a new date. To shift existing schedule dates by
> a fixed number of days, use something starting with double plus at the
> prompt, for example ‘++8d’ or ‘++2w’.
When I try this, however, I always get re-scheduling from the current
date. I am using Org mode version 9.1.6 (9.1.6-48-gfe7619-elpa). Here's
how to reproduce:
1. Create minimal.org.el:
(setq debug-on-error t
debug-on-signal nil
debug-on-quit nil)
(add-to-list 'load-path "c:/Users/micha/.emacs.d/elpa/org-20180212")
2. emacs.exe -Q -l minimal-org.el
3. Create a test.org buffer:
* TODO Task
SCHEDULED: <2018-01-01 Mon>
4. Add it to the agenda files list with C-c [.
5. M-x org-agenda RET t results in
Global list of TODO items of type: ALL
Available with ‘N r’: (0)[ALL] (1)TODO (2)DONE
test: TODO Task
6. Move down to TODO Task and type m to mark
7. B s (bulk schedule). The minibuffer will state:
(Re)Schedule to Date+time [2018-02-11]: [cursor] => <2018-02-11 Sun>
8. ++1y. The right part of the minibuffer now states
<2019-02-11 Mon>
I expected <2019-01-01 Tue>
9. RET.
The task is now rescheduled to <2019-02-11 Mon> rather than <2019-01-01
Tue> as initially expected.
Am I doing something wrong here?
Thanks,
Michael Hoffman
next reply other threads:[~2018-02-12 3:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 3:02 Michael Hoffman [this message]
2018-04-26 23:34 ` Bulk re-scheduling in agenda view Bastien
2018-04-26 23:48 ` Michael Hoffman
2018-04-27 0:24 ` Bastien
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='p5r011$gl9$1@blaine.gmane.org' \
--to=gmane4-hoffman@sneakemail.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).