emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Konstantin Antipin <antipin.konstantin@googlemail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: timer for a task
Date: Tue, 26 May 2009 16:45:54 +0200	[thread overview]
Message-ID: <B7E55E8B-F150-4AA9-9E1B-4686E3FE3717@gmail.com> (raw)
In-Reply-To: <61176df0905260726g7397a370pdc30fb0b3cd067bb@mail.gmail.com>

On May 26, 2009, at 4:26 PM, Konstantin Antipin wrote:

> Carsten, thank you for explanation.
> Hopefully, I will get FSF papers soon.
> In a meanwhile, here is another patch that introduces following  
> changes:
>    In case we set effort estimate on the currently clocked item,
>    show message when time is up (notification is shown only once)
>     * Linux only: If libnotify is used - the standard notification
>       system in linux, then show notification with it.
>       Note: Additional package libnotify-bin should be installed.
>   Additionally, if variable org-clock-sound is set, interpret it as
> path to sound file
>   and play it (wav files only).
>     * If aplay (tool from alsa - standard linux sound system) is
> available play sound
>       with it (all type of files).
> So, if someone has interest in this features, please try it.
> I also would like to discuss If we want this functionality (sound and
> notification) in the core,
> or it is better to put it to the extension... Or, just introduce
> another variable that controls if we show notification or not...

I think we can put this into the core if:

- this will work without crashing on any system where Emacs runs on,
   i.e. if the re is no way to play a sound file, fall back to (ding)
   with a message or so...

> * As proposed by Daniel, give user an option to see total time, spend
> on the task instead of currently clocked time.
> In fact, this functionality requires refactoring of org-clock-sum
> function. Is it ok, if I do it?

Maybe you don't really need to refactor it:


will give you the total clocked time in minutes.

- Carsten

> best,
> Konstantin
> patch is made on the git version of orgmode.
> On Tue, May 26, 2009 at 3:18 PM, Carsten Dominik
> <carsten.dominik@gmail.com> wrote:
>> On May 25, 2009, at 5:43 PM, Konstantin Antipin wrote:
>>> Here is the patch to org-clock.el that does show estimated effort in
>>> the mode-line if it is set.  Like so: 01:20/01:30 (clocked
>>> time/estimated time)
>>>  It does it by:
>>>   * Setting new variable org-clock-effort in org-clock-in function.
>>>   * If org-clock-effort is not nil, show estimated effort in the
>>> mode-line.
>>> I would like to go further and do the following:
>>> * Make a beep/or highlight if we spend more time on a task that
>>> initially intended
>>> * As proposed by Daniel, give user an option to see total time,  
>>> spend
>>> on the task instead of currently clocked time.
>>> Does somebody else need this? Will this changes be accepted to the
>>> orgmode-core?
>>> I just saw that in order to contribute, you need to sign some  
>>> papers..
>>> Is this the only way?
>>> I am new to open-source, so I am not really familiar with such  
>>> things.
>> Hi Konstantin,
>> this is interesting functionality which I would like to have in the  
>> core.
>> I can accept short patches of only a few lines without the  
>> paperwork, but
>> your patch is already at the limit, and adding the other ideas you  
>> have
>> will push it over that limit.  We have the following possibilities:
>> 1. You sign the papers.  This is very simple to do, unless you have
>>   an employer who owns everything you do and who might make problems.
>>   This would be my preferred solution.
>> 2. I can put stuff without FSF copyright assignment into the
>>   contrib directory - you could make a little package that hooks
>>   into Org, I would created any hooks needed.
>> 3. I treat your contribution as an "idea/feature request" and  
>> implement
>>   it myself.  As I have many other things to do, this is my least  
>> preferred
>>   solution.
>> If you decide to sign the papers, please get the form from the  
>> homepage
>> orgmode.org (near te end) and send it to the FSF, with a CC to me.   
>> This
>> will take you no more than 2 minutes.  We can then proceed with  
>> integrating
>> your stuff into the Org core, but I will be able to integrate this  
>> change
>> into Emacs only after I receive confirmation about the signed  
>> paper, which
>> will happen within a fee weeks or so.
>> - Carsten
>>> best,
>>> Konstantin
>>> On Mon, May 25, 2009 at 12:44 PM, Eraldo Helal <admin@eraldo.at>  
>>> wrote:
>>>> Sounds good to me.
>>>> Eraldo
>>>> On Mon, May 25, 2009 at 12:30, Konstantin Antipin
>>>> <antipin.konstantin@googlemail.com> wrote:
>>>>> Hi Daniel,
>>>>> Yes, you are right indeed. I am talking about effort estimates -  
>>>>> I'v
>>>>> missed this chapter for some reason from the manual.
>>>>> I like the idea you proposed - to show how much time is left in  
>>>>> the
>>>>> mode line. And I think I am going to write necessary code for  
>>>>> this.
>>>>> Or, may be someone has even better idea?
>>>>> best,
>>>>> Konstantin
>>>>> On Mon, May 25, 2009 at 11:25 AM, Daniel Clemente <n142857@gmail.com 
>>>>> >
>>>>> wrote:
>>>>>> Hi.
>>>>>>  I suppose you talk about estimated efforts. I also have  
>>>>>> noticed that I
>>>>>> work better if I have defined them, but it is very easy to miss  
>>>>>> them and
>>>>>> work on a task more time than planned.
>>>>>>  An easy improvement would be to show at the mode line not only  
>>>>>> how
>>>>>> much time you have worked on the current task but also the  
>>>>>> remaining time
>>>>>> according to your effort estimate. And if it comes to 0,  
>>>>>> highlight it
>>>>>> noticeably.
>>>>>>  Other useful things to show would be the *total* elapsed time  
>>>>>> (not
>>>>>> only the elapsed time of the last C-c C-x C-i) or directly the  
>>>>>> effort
>>>>>> estimate (instead of the remaining time, the total time).
>>>>>>  And as you say, an alarm would be useful.
>>>>>> -- Daniel
>>>>>> El dl, mai 25 2009, Konstantin Antipin va escriure:
>>>>>>> Hi everybody!
>>>>>>> I am constantly trying to be more productive, and there is one  
>>>>>>> thing
>>>>>>> that I noticed:
>>>>>>> If you give yourself a specific time for a task, then you tend  
>>>>>>> to
>>>>>>> finish this task in this time. It helps to stay focused and do  
>>>>>>> stuff
>>>>>>> that is most important.
>>>>>>> So, the question is - Is there any way to set a timer on a  
>>>>>>> taks, and
>>>>>>> get a bell when it is expired?
>>>>>>> Some time before I even wrote a small extension that helps me  
>>>>>>> to do
>>>>>>> that http://www.emacswiki.org/emacs/tea-time
>>>>>>> But now I am thinking - is there an orgmode-way to do that? It  
>>>>>>> would
>>>>>>> be great to integrate it with great time tracking system, for
>>>>>>> example...
>>>>>>> If nobody uses proposed feature, please give me a hint how it  
>>>>>>> would be
>>>>>>> best to do that.
>>>>>>> my best,
>>>>>>> Konstantin
>>>>>>> _______________________________________________
>>>>>>> Emacs-orgmode mailing list
>>>>>>> Remember: use `Reply All' to send replies to the list.
>>>>>>> Emacs-orgmode@gnu.org
>>>>>>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>>>> _______________________________________________
>>>>> Emacs-orgmode mailing list
>>>>> Remember: use `Reply All' to send replies to the list.
>>>>> Emacs-orgmode@gnu.org
>>>>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>> <clock-efforts.patch>_______________________________________________
>>> Emacs-orgmode mailing list
>>> Remember: use `Reply All' to send replies to the list.
>>> Emacs-orgmode@gnu.org
>>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
> <clock-effort-notify.patch>

  reply	other threads:[~2009-05-26 14:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-25  8:40 timer for a task Konstantin Antipin
2009-05-25  9:25 ` Daniel Clemente
2009-05-25 10:30   ` Konstantin Antipin
2009-05-25 10:44     ` Eraldo Helal
2009-05-25 15:43       ` Konstantin Antipin
2009-05-26 13:18         ` Carsten Dominik
2009-05-26 14:26           ` Konstantin Antipin
2009-05-26 14:45             ` Carsten Dominik [this message]
2009-05-26 22:13               ` Konstantin Antipin
2009-05-27  4:27                 ` Carsten Dominik
2009-05-27 13:32                   ` Bernt Hansen
2009-05-28  0:02                     ` Konstantin Antipin

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:

  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=B7E55E8B-F150-4AA9-9E1B-4686E3FE3717@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=antipin.konstantin@googlemail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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