emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Maxim Baz <z0rch.coding@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: bulk TODO state change creates a LOGBOOK state change note only for one task
Date: Fri, 06 Feb 2015 09:54:56 +0100	[thread overview]
Message-ID: <871tm31ktb.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAN0DYZ0aa261YiNt1oX3=TfNpaSnc1ojdU+V0609FWWJWGCFrg@mail.gmail.com> (Maxim Baz's message of "Wed, 04 Feb 2015 21:41:35 +0000")

Hello,

Maxim Baz <z0rch.coding@gmail.com> writes:

> I expect org-mode to create such "state change" note in LOGBOOK drawer for
> every task I'm changing.
>
> Now I'll describe my steps in a bit more detailed way, and afterwards you
> will find the system information I use.
>
> 1. emacs -Q -l ~/org-minimal.el ~/test.org
> 2. Create 3 tasks:
>     * TODO task1
>     * TODO task2
>     * TODO task3
> 3. M-x -> org-agenda-file-to-front
> 3. M-x -> org-agenda -> t
> 4. Mark those 3 tasks
> 5. M-x -> org-agenda-bulk-action -> t -> NEXT
>
> The ACTUAL contents of ~/test.org is:
>
>     * NEXT task1
>     * NEXT task2
>     * NEXT task3
>     :LOGBOOK:
>     - State "NEXT"       from "TODO"       [2015-02-04 Wed 22:11]
>     :END:
>
> The EXPECTED contents of ~/test.org is:
>
>     * NEXT task1
>     :LOGBOOK:
>     - State "NEXT"       from "TODO"       [2015-02-04 Wed 22:11]
>     :END:
>     * NEXT task2
>     :LOGBOOK:
>     - State "NEXT"       from "TODO"       [2015-02-04 Wed 22:11]
>     :END:
>     * NEXT task3
>     :LOGBOOK:
>     - State "NEXT"       from "TODO"       [2015-02-04 Wed 22:11]
>     :END:

This should be fixed. Thank you.


Regards,

-- 
Nicolas Goaziou

next prev parent reply	other threads:[~2015-02-06  8:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-04 21:41 Bug: bulk TODO state change creates a LOGBOOK state change note only for one task Maxim Baz
2015-02-05 16:38 ` Yuri Niyazov
2015-02-06  8:54 ` Nicolas Goaziou [this message]
2015-02-06 10:52   ` Maxim Baz

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=871tm31ktb.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=z0rch.coding@gmail.com \
    /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

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).