From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [bug] Remote durations are considered as fractions
Date: Thu, 19 Apr 2012 15:19:57 +0200 [thread overview]
Message-ID: <80hawfj1tu.fsf@somewhere.org> (raw)
In-Reply-To: 87y5q3b3xf.fsf@gnu.org
Hi Bastien,
Bastien wrote:
> "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>
>> Using the flag T does not help:
>>
>> | Planning | 00:00:03 |
>> | Reporting | 00:00:09 |
>> #+TBLFM: @1$2=remote(hours-spent,@4$4);T
>
> This should work as expected now (with the "T" flag.)
I confirm this is now working as expected for both the "T" and the "t" flags:
- Using the flag T:
| Planning | 03:36:00 |
| Reporting | 09:03:00 |
#+TBLFM: @1$2=remote(hours-spent,@4$3);T::@2$2=remote(hours-spent,@8$3);T
- Using the flag t:
| Planning | 3.60 |
| Reporting | 9.05 |
#+TBLFM: @1$2=remote(hours-spent,@4$3);t::@2$2=remote(hours-spent,@8$3);t
Thanks!
BTW, *could we limit the format of "T" to H:MM*, instead of H:MM:SS? The first
case seems much more common, and the one used in all time clocking functions
of Org.
> Note that the conversion of 3:12 into 1:4 is independant of getting the
> remote references right when they are durations.
>
> | Test | 3:12 |
> | | 1:4 |
> #+TBLFM: @2$2=@1$2
>
> Thanks for reporting this!
Wasn't aware of that. Thanks for mentioning.
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2012-04-19 13:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 12:35 [bug] Remote durations are considered as fractions Sebastien Vauban
2012-04-10 22:46 ` Bastien
2012-04-19 13:19 ` Sebastien Vauban [this message]
2012-04-20 11:21 ` Bastien
2012-04-20 20:45 ` Sebastien Vauban
2012-04-20 23:22 ` Bastien
2012-05-02 10:32 ` Sebastien Vauban
2012-05-09 19:16 ` Sebastien Vauban
2012-06-04 15:02 ` Sebastien Vauban
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=80hawfj1tu.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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 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).