Bug: Bulk reschedule with reschedule logging on fails [8.3.4 (8.3.4-5-gdc68d2-elpaplus @ /home/tyria/.emacs.d/elpa/org-plus-contrib-20160229/)]

Bug: Bulk reschedule with reschedule logging on fails [8.3.4 (8.3.4-5-gdc68d2-elpaplus @ /home/tyria/.emacs.d/elpa/org-plus-contrib-20160229/)]

[Allen Li]

When bulk rescheduling TODO items with org-log-reschedule set to 'note,
only the first marked item will get rescheduled.  I have reproduced this
on a fresh clone of the Git repo with a minimal config.

Here is the *Messages* snippet:

  Org-mode version 8.3.4 (release_8.3.4-635-g268486 @ /<snipped>/org-mode/lisp/)
  Press key for agenda command (unrestricted):
  1 entries marked for bulk action
  2 entries marked for bulk action
  Bulk: [$]arch [A]rch->sib [t]odo [+/-]tag [s]chd [d]eadline [r]efile [S]catter [f]unction    
  Scheduled to <2016-03-09 Wed> [2 times]
  Skipping removed entry at #<marker (moves after insertion) at 42 in test.org>
  Acted on 1 entries, skipped 1 (disappeared before their turn)
  Note store

Here is the config:

  (add-to-list 'load-path (expand-file-name "~/<snipped>/org-mode/lisp"))
  (add-to-list 'auto-mode-alist '("\\.\\(org\\  |org_archive\\|txt\\)$" . org-mode))
  (setq org-agenda-files '("/tmp/test.org"))
  (require 'org-install)
  (require 'org-habit)

  (global-set-key "\C-cl" 'org-store-link)
  (global-set-key "\C-ca" 'org-agenda)
  (global-set-key "\C-cb" 'org-iswitchb)

  (setq org-log-reschedule 'note)

Emacs  : GNU Emacs 24.5.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.16.6)
 of 2015-09-09 on foutrelis

Re: Bug: Bulk reschedule with reschedule logging on fails [8.3.4 (8.3.4-5-gdc68d2-elpaplus @ /home/tyria/.emacs.d/elpa/org-plus-contrib-20160229/)]

[Nicolas Goaziou]

Hello,

Allen Li <darkfeline@felesatra.moe> writes:

> When bulk rescheduling TODO items with org-log-reschedule set to 'note,
> only the first marked item will get rescheduled.  I have reproduced this
> on a fresh clone of the Git repo with a minimal config.
>
> Here is the *Messages* snippet:
>
>   Org-mode version 8.3.4 (release_8.3.4-635-g268486 @ /<snipped>/org-mode/lisp/)
>   Press key for agenda command (unrestricted):
>   1 entries marked for bulk action
>   2 entries marked for bulk action
>   Bulk: [$]arch [A]rch->sib [t]odo [+/-]tag [s]chd [d]eadline [r]efile [S]catter [f]unction    
>   Scheduled to <2016-03-09 Wed> [2 times]
>   Skipping removed entry at #<marker (moves after insertion) at 42 in test.org>
>   Acted on 1 entries, skipped 1 (disappeared before their turn)
>   Note store
>
> Here is the config:
>
>   (add-to-list 'load-path (expand-file-name "~/<snipped>/org-mode/lisp"))
>   (add-to-list 'auto-mode-alist '("\\.\\(org\\  |org_archive\\|txt\\)$" . org-mode))
>   (setq org-agenda-files '("/tmp/test.org"))
>   (require 'org-install)
>   (require 'org-habit)
>
>   (global-set-key "\C-cl" 'org-store-link)
>   (global-set-key "\C-ca" 'org-agenda)
>   (global-set-key "\C-cb" 'org-iswitchb)
>
>   (setq org-log-reschedule 'note)

I cannot reproduce it with the following "test.org":

 * TODO A
 * TODO B

Could you also provide the "test.org" you are using? Thank you.


Regards,

-- 
Nicolas Goaziou

Re: Bug: Bulk reschedule with reschedule logging on fails [8.3.4 (8.3.4-5-gdc68d2-elpaplus @ /home/tyria/.emacs.d/elpa/org-plus-contrib-20160229/)]

[Allen Li]

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


The TODO items need to be scheduled first (since it's the REschedule
that is causing it).  Can you try:

* TODO A
SCHEDULED: <2016-01-01 Mon>
* TODO B
SCHEDULED: <2016-01-01 Mon>

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Hello,
>
> Allen Li <darkfeline@felesatra.moe> writes:
>
>> When bulk rescheduling TODO items with org-log-reschedule set to 'note,
>> only the first marked item will get rescheduled.  I have reproduced this
>> on a fresh clone of the Git repo with a minimal config.
>>
>> Here is the *Messages* snippet:
>>
>>   Org-mode version 8.3.4 (release_8.3.4-635-g268486 @ /<snipped>/org-mode/lisp/)
>>   Press key for agenda command (unrestricted):
>>   1 entries marked for bulk action
>>   2 entries marked for bulk action
>>   Bulk: [$]arch [A]rch->sib [t]odo [+/-]tag [s]chd [d]eadline [r]efile [S]catter [f]unction
>>   Scheduled to <2016-03-09 Wed> [2 times]
>>   Skipping removed entry at #<marker (moves after insertion) at 42 in test.org>
>>   Acted on 1 entries, skipped 1 (disappeared before their turn)
>>   Note store
>>
>> Here is the config:
>>
>>   (add-to-list 'load-path (expand-file-name "~/<snipped>/org-mode/lisp"))
>>   (add-to-list 'auto-mode-alist '("\\.\\(org\\  |org_archive\\|txt\\)$" . org-mode))
>>   (setq org-agenda-files '("/tmp/test.org"))
>>   (require 'org-install)
>>   (require 'org-habit)
>>
>>   (global-set-key "\C-cl" 'org-store-link)
>>   (global-set-key "\C-ca" 'org-agenda)
>>   (global-set-key "\C-cb" 'org-iswitchb)
>>
>>   (setq org-log-reschedule 'note)
>
> I cannot reproduce it with the following "test.org":
>
>  * TODO A
>  * TODO B
>
> Could you also provide the "test.org" you are using? Thank you.
>
>
> Regards,


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]

Re: Bug: Bulk reschedule with reschedule logging on fails [8.3.4 (8.3.4-5-gdc68d2-elpaplus @ /home/tyria/.emacs.d/elpa/org-plus-contrib-20160229/)]

[Nicolas Goaziou]

Hello,

Allen Li <darkfeline@felesatra.moe> writes:

> The TODO items need to be scheduled first (since it's the REschedule
> that is causing it).  Can you try:
>
> * TODO A
> SCHEDULED: <2016-01-01 Mon>
> * TODO B
> SCHEDULED: <2016-01-01 Mon>

I can now reproduce it.

This raises another question, though. What is a reasonable behaviour for
bulk schedule+log?

Regards,

-- 
Nicolas Goaziou

Re: Bug: Bulk reschedule with reschedule logging on fails [8.3.4 (8.3.4-5-gdc68d2-elpaplus @ /home/tyria/.emacs.d/elpa/org-plus-contrib-20160229/)]

[Allen Li]

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


Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>
> This raises another question, though. What is a reasonable behaviour for
> bulk schedule+log?

I can think of three reasonable options:

1. Prompt for a note, then apply it to all affected items.
2. Prompt for a note, then apply it only to items that are already
   scheduled (and hence rescheduled).
3. Don't attempt to add a note and just add timestamps.

Then there's the unreasonable option:

4. Prompt for a note for each item.

If I had to pick, I'd go with 2, but any of 1-3 is fine.  In this case,
having bulk scheduling work is more important than whether
org-log-reschedule is being faithfully applied, in my opinion.

Allen

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]

Re: Bug: Bulk reschedule with reschedule logging on fails [8.3.4 (8.3.4-5-gdc68d2-elpaplus @ /home/tyria/.emacs.d/elpa/org-plus-contrib-20160229/)]

[Nicolas Goaziou]

Hello,

Allen Li <darkfeline@felesatra.moe> writes:

> I can think of three reasonable options:
>
> 1. Prompt for a note, then apply it to all affected items.
> 2. Prompt for a note, then apply it only to items that are already
>    scheduled (and hence rescheduled).
> 3. Don't attempt to add a note and just add timestamps.
>
> Then there's the unreasonable option:
>
> 4. Prompt for a note for each item.

No worries. This is not possible without rewriting a large part of the
log notes innards.

> If I had to pick, I'd go with 2, but any of 1-3 is fine.  In this case,
> having bulk scheduling work is more important than whether
> org-log-reschedule is being faithfully applied, in my opinion.

It is fixed, with option 3. Global note doesn't sound like a silver
bullet. Also, 3 was much easier to implement.

Thank you for the feedback.


Regards,

-- 
Nicolas Goaziou

Re: Bug: Bulk reschedule with reschedule logging on fails

[Allen Li]

Hello,

I'm replying to a very old thread about a bug.  Hopefully I haven't
munged the headers.  Following is a summary of the thread.

Allen Li writes:

> When bulk rescheduling TODO items with org-log-reschedule set to
> 'note, only the first marked item will get rescheduled.  I have
> reproduced this on a fresh clone of the Git repo with a minimal
> config.

Nicolas Goaziou writes:

> I can now reproduce it.

> This raises another question, though. What is a reasonable behaviour for
> bulk schedule+log?

Allen Li writes:

> I can think of three reasonable options:
>
> 1. Prompt for a note, then apply it to all affected items.
> 2. Prompt for a note, then apply it only to items that are already
>    scheduled (and hence rescheduled).
> 3. Don't attempt to add a note and just add timestamps.

Nicolas Goaziou writes:

> It is fixed, with option 3. Global note doesn't sound like a silver
> bullet. Also, 3 was much easier to implement.

I believe that this bug has not been fixed for ‘org-log-redeadline’ as I
have encountered it recently, but I have not done a clean repro of it
yet (although I think such a repro may not be necessary).

Re: Bug: Bulk reschedule with reschedule logging on fails

[Nicolas Goaziou]

Hello,

Allen Li <darkfeline@felesatra.moe> writes:

> Allen Li writes:
>
>> I can think of three reasonable options:
>>
>> 1. Prompt for a note, then apply it to all affected items.
>> 2. Prompt for a note, then apply it only to items that are already
>>    scheduled (and hence rescheduled).
>> 3. Don't attempt to add a note and just add timestamps.
>
> Nicolas Goaziou writes:
>
>> It is fixed, with option 3. Global note doesn't sound like a silver
>> bullet. Also, 3 was much easier to implement.
>
> I believe that this bug has not been fixed for ‘org-log-redeadline’ as I
> have encountered it recently, but I have not done a clean repro of it
> yet (although I think such a repro may not be necessary).

Correct. Fixed, this time. Thanks for the heads-up.

Regards,

-- 
Nicolas Goaziou