emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Yuri Niyazov <yuri.niyazov@gmail.com>
To: Maxim Baz <z0rch.coding@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Bug: bulk TODO state change creates a LOGBOOK state change note only for one task
Date: Thu, 5 Feb 2015 08:38:25 -0800	[thread overview]
Message-ID: <CACbjG0sM1_VikDbqbjCcvRJVe4_bOfZrmYcMU-D36wO1vS_MDA@mail.gmail.com> (raw)
In-Reply-To: <CAN0DYZ0aa261YiNt1oX3=TfNpaSnc1ojdU+V0609FWWJWGCFrg@mail.gmail.com>

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

I can confirm - this has happened to me too

On Wednesday, February 4, 2015, Maxim Baz <z0rch.coding@gmail.com> wrote:

> The important piece of org-mode configuration is:
>
>     org-minimal.el
>
>     (setq org-todo-keywords '(
>       (sequence "TODO(t)" "NEXT(n!)" "|" "DONE(d)")))
>
> So I expect the following note to appear in LOGBOOK once I change the
> state from TODO to NEXT:
>
>     :LOGBOOK:
>     - State "NEXT"       from "TODO"       [2015-02-04 Wed 22:11]
>     :END:
>
> It works perfectly fine if I change a state of a single task.
> But if select multiple TODO tasks in Agenda view and change all of them to
> NEXT in bulk, only the last task will have such "state change" record.
>
> 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:
>
> Emacs: GNU Emacs 25.0.50.1 (x86_64-pc-linux-gnu, GTK+ Version 3.12.2) of
> 2015-01-09 on lgw01-32
> Package: Org-mode version 8.3beta (release_8.3beta-794-g55c070 @
> /home/z0rch/.emacs.d/el-get/org-mode/lisp/)
>
>

[-- Attachment #2: Type: text/html, Size: 3148 bytes --]

  reply	other threads:[~2015-02-05 16:38 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 [this message]
2015-02-06  8:54 ` Nicolas Goaziou
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=CACbjG0sM1_VikDbqbjCcvRJVe4_bOfZrmYcMU-D36wO1vS_MDA@mail.gmail.com \
    --to=yuri.niyazov@gmail.com \
    --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
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).