From: Nick Guiffrida <goodfella005@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Properties do not show up in clock table [9.0.6 (9.0.6-elpa @ /home/nick/.emacs.d/elpa/org-20170502/)]
Date: Sun, 7 May 2017 08:27:58 -0700 [thread overview]
Message-ID: <CADq1DN99nyiiE7zmhYGNwE0b8U99FGakfPx-eySwRdW2xoUCpA@mail.gmail.com> (raw)
In-Reply-To: <877f1t7zot.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1123 bytes --]
Thank you Nicholas, when I get a chance I'll try that.
On May 7, 2017 3:01 AM, "Nicolas Goaziou" <mail@nicolasgoaziou.fr> wrote:
> Hello,
>
> Nick Guiffrida <goodfella005@gmail.com> writes:
>
> > Below is content which that can be used to reproduce my problem:
> >
> > * Job1
> >> :PROPERTIES:
> >> :job-number: 123457
> >> :END:
> >> :LOGBOOK:
> >> CLOCK: [2017-05-06 Sat 18:59]--[2017-05-06 Sat 19:30] => 0:31
> >> :END:
> >> #+BEGIN: clocktable :maxlevel 2 :scope file :properties ("job-number")
> >> #+CAPTION: Clock summary at [2017-05-06 Sat 19:54]
> >> | job-number | Headline | Time | |
> >> |------------+--------------+--------+-----|
> >> | | *Total time* | *0:31* | 0.0 |
> >> |------------+--------------+--------+-----|
> >> | | Job1 | 0:31 | 0.0 |
> >> #+TBLFM: $4='(org-clock-time% @2$2 $2..$3);%.1f
> >> #+END:
> >>
> >
> > You can see that the 'job-number' property is not in the clock table.
>
> The bug doesn't appear in master (i.e., development branch). You may
> want to test it or wait for Org 9.1 to be released.
>
> Regards,
>
> --
> Nicolas Goaziou
>
[-- Attachment #2: Type: text/html, Size: 1741 bytes --]
prev parent reply other threads:[~2017-05-07 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-07 3:06 Bug: Properties do not show up in clock table [9.0.6 (9.0.6-elpa @ /home/nick/.emacs.d/elpa/org-20170502/)] Nick Guiffrida
2017-05-07 10:01 ` Nicolas Goaziou
2017-05-07 15:27 ` Nick Guiffrida [this message]
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=CADq1DN99nyiiE7zmhYGNwE0b8U99FGakfPx-eySwRdW2xoUCpA@mail.gmail.com \
--to=goodfella005@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).