From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Allen Li <darkfeline@felesatra.moe>
Cc: emacs-orgmode@gnu.org
Subject: 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/)]
Date: Wed, 16 Mar 2016 22:11:04 +0100 [thread overview]
Message-ID: <87vb4mw2l3.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87d1qwzbvl.fsf@jakuri.felesatra.moe> (Allen Li's message of "Mon, 14 Mar 2016 19:57:34 -0700")
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
next prev parent reply other threads:[~2016-03-16 21:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 4:17 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
2016-03-10 9:49 ` Nicolas Goaziou
2016-03-11 5:16 ` Allen Li
2016-03-13 19:54 ` Nicolas Goaziou
2016-03-15 2:57 ` Allen Li
2016-03-16 21:11 ` Nicolas Goaziou [this message]
2017-05-09 6:38 ` Bug: Bulk reschedule with reschedule logging on fails Allen Li
2017-05-11 22:41 ` Nicolas Goaziou
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vb4mw2l3.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=darkfeline@felesatra.moe \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.