From: Alex Bochannek <alexb@juniper.net>
To: emacs-orgmode@gnu.org
Subject: Re: Suggested change to round timestamps.
Date: Wed, 15 Mar 2006 13:34:14 -0800 [thread overview]
Message-ID: <uk6avo0ix.fsf@juniper.net> (raw)
In-Reply-To: <87lkvbh0y4.fsf@sarge.yax.org.uk> (Philip Rooke's message of "Wed, 15 Mar 2006 21:06:59 +0000")
Philip Rooke <phil@yax.org.uk> writes:
> Thomas Baumann <thomas.baumann@ch.tum.de> writes:
>
>> Useful, maybe, for accounting purposes, in this case, the calculation of
>> the timespan in between could be extended to compute and insert a
>> rounded value.
>
> I agree, definitely a useful extension. I know a number of people who
> log/record time to larger units than 1 minute (6 minutes seems to be
> common).
It seems like people get used to that when they work in environments
that requires them to submit time cards. Personally, I just find it
annoying to look at the agenda view and see a meeting I attended
listed as 13:02-14:07 :-)
>> For other purposes I would stay with the exact value (which of course
>> is still possible in Alex version)
>
> Likewise, I would stay with the exact value but still like the idea of
> being able to do something different.
I tried to change it in a way that would not affect the existing
functionality. I also looked at all the calls to current-time (in the
4.01 version I started with) and only modified the ones that were
relevant. I did not look at 4.09/4.10 yet.
Alex.
next prev parent reply other threads:[~2006-03-15 21:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 8:16 Suggested change to round timestamps Thomas Baumann
2006-03-15 21:06 ` Philip Rooke
2006-03-15 21:34 ` Alex Bochannek [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-13 23:43 Alex Bochannek
2006-03-15 7:23 ` Carsten Dominik
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=uk6avo0ix.fsf@juniper.net \
--to=alexb@juniper.net \
--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 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).