emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Lundin <mdl@imapmail.org>
To: Ilya Shlyakhter <ilya_shl@alum.mit.edu>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: suggestion: options for chronological agenda
Date: Sat, 26 Sep 2009 07:57:40 -0400	[thread overview]
Message-ID: <m21vltgbpn.fsf@fastmail.fm> (raw)
In-Reply-To: <4b11f87e0909252202m93e3659gbc6d9c37c35be174@mail.gmail.com> (Ilya Shlyakhter's message of "Sat, 26 Sep 2009 01:02:52 -0400")

Ilya Shlyakhter <ilya_shl@alum.mit.edu> writes:

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

I believe that's because org-mode, in general, treats active timestamps
as scheduling data -- i.e., things you need to do. I.e., it is optimized
for using inactive timestamps to indicate "recently worked on" items.

>     - it looks at the _first_ timestamp in an entry, rather than the
> _last_ timestamp

Could you give an example? When I try C-c a L, it creates separate
instances for each timestamp in an entry.

E.g., the following file...

--8<---------------cut here---------------start------------->8---
* A test
<2009-09-25 Fri>
<2009-09-26 Sat>
--8<---------------cut here---------------end--------------->8---

becomes...

--8<---------------cut here---------------start------------->8---
Friday     25 September 2009
  A test
-------------------------------------------------------------------------------
Saturday   26 September 2009
  A test
--8<---------------cut here---------------end--------------->8---

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

Depending on whether or not Carsten decides to change the behavior of
the timeline view ;) , you could always use a custom agenda command to
accomplish the same thing.

>
> The suggestion is to enhance the timeline agenda with options to:
>    - recognize "inactive" timestamps ([in square brackets])

See the variable org-agenda-inactive-timestamps.

> It would also be _really_ great if the chronological listing could be
> filtered to contain only entries matching a certain tag/property
> query.

Try filtering the timeline with "/".

Best,
Matt

  reply	other threads:[~2009-09-26 11:57 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 [this message]
2009-09-26 12:52   ` Matthew Lundin
2009-09-28 20:10 ` Carsten Dominik
2009-09-29  2:54   ` Ilya Shlyakhter

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=m21vltgbpn.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=ilya_shl@alum.mit.edu \
    /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).