From: Ilya Shlyakhter <ilya_shl@alum.mit.edu>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: suggestion: options for chronological agenda
Date: Mon, 28 Sep 2009 22:54:33 -0400 [thread overview]
Message-ID: <4b11f87e0909281954p7a278cbemdcb5ccac2bd00b5@mail.gmail.com> (raw)
In-Reply-To: <4A73538F-84B1-4E48-B566-5D0BD5DE182F@gmail.com>
Ah, didn't know about that. Things have changed since I last read
the full manual :)
Thanks for help!
ilya
On Mon, Sep 28, 2009 at 4:10 PM, Carsten Dominik
<carsten.dominik@gmail.com> wrote:
> Hi Ilya,
>
> have you tried
>
> C-a a to get the agenda,
>
> and then
>
> v [
>
> to include inactive time stamps?
>
> HTH
>
> - Carsten
>
> On Sep 26, 2009, at 6:02 AM, Ilya Shlyakhter wrote:
>
>> I often need to find recently modified entries. I try to timestamp
>> entries I work on with the active timestamps
>> (in angular brackets), and use the C-x a L command. This mostly
>> works, but is imperfect:
>> - when i use time logging, it inserts "inactive" timestamps that
>> are not found this way. so, i can't use this to find
>> "recently worked on" entries.
>> - it looks at the _first_ timestamp in an entry, rather than the
>> _last_ timestamp
>> - it is limited to one file . would be much better if it could
>> be made to work across the entire agenda.
>> - it would be fine to have the option to limit it to entries
>> within the last, say, week, if that would speed it up.
>>
>> The suggestion is to enhance the timeline agenda with options to:
>> - recognize "inactive" timestamps ([in square brackets])
>> - use last, rather than first, timestamp in an entry
>> - search the entire agenda, rather than just the current file
>> - limit the agenda to entries within the last (say) week.
>>
>> The timeview agenda was of course originally designed for another use
>> case -- as a personal calendar/diary.
>> But I'm finding myself repeatedly using it this way: organize the
>> entries by hierarchical subject, and use the timeline
>> agenda to generate a chronological listing.
>>
>> It would also be _really_ great if the chronological listing could be
>> filtered to contain only entries matching a certain
>> tag/property query. Then you could e.g. get a chronological list of
>> "important" entries, or entries on a certain
>> subject.
>>
>> ilya
>>
>>
>> _______________________________________________
>> 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
>
>
prev parent reply other threads:[~2009-09-29 2:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-26 5:02 suggestion: options for chronological agenda Ilya Shlyakhter
2009-09-26 11:57 ` Matt Lundin
2009-09-26 12:52 ` Matthew Lundin
2009-09-28 20:10 ` Carsten Dominik
2009-09-29 2:54 ` Ilya Shlyakhter [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=4b11f87e0909281954p7a278cbemdcb5ccac2bd00b5@mail.gmail.com \
--to=ilya_shl@alum.mit.edu \
--cc=carsten.dominik@gmail.com \
--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).