emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] Bug: Bulk re-scheduling to a relative offset doesn't work [9.1.6


From: Nicolas Goaziou
Subject: Re: [O] Bug: Bulk re-scheduling to a relative offset doesn't work [9.1.6 (9.1.6-48-gfe7619-elpa @ c:/Users/micha/.emacs.d/elpa/org-20180212/)]
Date: Thu, 01 Mar 2018 10:56:56 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux)

Hello,

Michael Hoffman <address@hidden> writes:

> I previously asked a question about this on emacs-orgmode but it seems
> more likely that this is a bug.
>
> https://lists.gnu.org/archive/html/emacs-orgmode/2018-02/msg00183.html
>
> 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.

Fixed. Thank you.

Regards,

-- 
Nicolas Goaziou



reply via email to

[Prev in Thread] Current Thread [Next in Thread]