From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: org-clock-select-task: how does it work?
Date: Wed, 28 Jan 2015 13:52:09 +0100 [thread overview]
Message-ID: <8661brt6di.fsf@example.com> (raw)
In-Reply-To: 87mw53xhzq.fsf@gmail.com
Tory S. Anderson wrote:
> Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org> writes:
>> Peter Münster wrote:
>>> On Sat, Jan 24 2015, Peter Münster wrote:
>>>
>>>> - There are duplicates in the list.
>>>
>>> Not reproducible.
>>
>> I still do have duplicates in my list as well. It never has been fixed,
>> but I don't have either a reproducible recipe.
>>
>> See https://lists.gnu.org/archive/html/emacs-orgmode/2013-04/msg00568.html.
>
> Now I'm loving this tool but I'm looking for two tweaks that would
> make a big difference.
>
> 1) I use "work.org" to track my weekly work hours; each week is mostly
> the same tasks, but new time frames. I need to be able to make sure my
> "recent clock list" is talking about the item for this week, not the
> identically named item for a previous week. If I could see the
> tree-path of the items (in the same way putting the point over an item
> in agenda shows you the hierarchy) that would be great.
Not sure I'd like that, or at least not always / by default. That'd make
tasks become truncated or going on multiple lines in my case.
Dunno what would be the best for all of us.
> 2) As Peter originally mentioned, I see only five tasks on the list;
> I have more than that each week. Can this be expanded with some
> variable?
--8<---------------cut here---------------start------------->8---
;; Number of clock tasks to remember in history.
(setq org-clock-history-length 35) ; 1 to 9 + A to Z
--8<---------------cut here---------------end--------------->8---
Though, I don't understand why it's never that long -- while it should
grow up to that amount before forgetting about old tasks.
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2015-01-28 12:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-24 13:57 org-clock-select-task: how does it work? Peter Münster
2015-01-24 15:08 ` Tory S. Anderson
2015-01-24 15:30 ` Peter Münster
2015-01-24 15:42 ` Tory S. Anderson
2015-01-24 19:35 ` Peter Münster
2015-01-24 20:15 ` Peter Münster
2015-01-27 10:00 ` Sebastien Vauban
2015-01-28 11:27 ` Tory S. Anderson
2015-01-28 12:52 ` Sebastien Vauban [this message]
2015-01-28 13:15 ` Marco Wahl
2015-01-28 13:26 ` Tory S. Anderson
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=8661brt6di.fsf@example.com \
--to=sva-news-d0wtavr13harg/idocfnwg@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).