From: Matt Lundin <mdl@imapmail.org>
To: Paul Sexton <psexton@xnet.co.nz>
Cc: emacs-orgmode@gnu.org
Subject: Re: Patch: More options for ignoring scheduled items in agenda todo lists
Date: Sat, 15 Jan 2011 09:26:11 -0500 [thread overview]
Message-ID: <87aaj2kzuk.fsf@fastmail.fm> (raw)
In-Reply-To: 4D30E811.4090508@xnet.co.nz
Paul Sexton <psexton@xnet.co.nz> writes:
> Thanks for your reply Matt.
>> I believe this patch would require many users to change their existing
>> configurations.
>>
>> I rely on the "past" setting when creating block agenda views, such as
>> an agenda that includes everything scheduled today or earlier together
>> with a todo list that includes everything else (i.e., unscheduled or
>> scheduled in the future). If the definition of past is changed, I will
>> end up with a lot of duplicate items in the block agenda.
>>
> You just need to change 'past' to 'notfuture'. 'Past' is not an
> accurate description of the behaviour of the setting -- it actually
> ignores past+present, and there is no way to only ignore past items.
Linguistic precision notwithstanding, my recommendation would be to
defer to convention here. Of course, I also defer to the maintainer. :)
According to the docstrings for org-agenda-todo-ignore-deadlines and
org-agenda-todo-ignore-scheduled, the definition of "past" includes
today:
,----
| past Don't show entries scheduled today or in the past.
| past Don't show entries with a deadline timestamp for today or in the past.
`----
I suppose my chief question is whether it would be possible to preserve
the current behavior of "past", while introducing a new setting to
accommodate the functionality you seek (e.g., "old" or, better yet,
integers)?
> Development of org mode often introduces incompatibilities with older
> versions. These are generally well highlighted in the release notes.
> All this change would require is for users to change 'past' to
> 'notfuture' when using this variable.
Indeed, it is relatively easy to change the settings with a search and
replace. Somewhat harder is catching all such changes in the release
notes. ;)
My concern has to do with the precedent this sets. I would submit that
incompatibilities be introduced only with the utmost caution and in
cases of clear need. If I remember correctly, obsoleted settings and
variables are usually gracefully deprecated (e.g., org-agenda-span vs.
org-agenda-ndays). If each release contains multiple small breakages
because individual users would like to change conventional naming, it
can become difficult to keep up with org-development. Of course, such
decisions are in the hands of the Bastien and Carsten.
> I just want to extend and logicalise' the functionality of this
> variable.
What do you think of the possibility of using positive and negative
integers (e.g., -1 for past only, 1 for future only, -7 for anything a
week or more in the past, 14 for anything two weeks or more in the
future, and so on)? Would that perhaps be a way to add some
comprehensive logic and fine-grained control to this setting? I'd be
happy to work up a patch to that effect.
Thanks for taking the time to respond to my questions!
Best,
Matt
next prev parent reply other threads:[~2011-01-15 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 22:46 Patch: More options for ignoring scheduled items in agenda todo lists Paul Sexton
2011-01-14 12:52 ` Matt Lundin
[not found] ` <4D30E811.4090508@xnet.co.nz>
2011-01-15 14:26 ` Matt Lundin [this message]
2011-01-17 20:51 ` [PATCH] Add new option for ignoring past or future items in the global todo list Matt Lundin
2011-01-18 0:46 ` Paul Sexton
2011-01-26 10:00 ` [Accepted] " 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=87aaj2kzuk.fsf@fastmail.fm \
--to=mdl@imapmail.org \
--cc=emacs-orgmode@gnu.org \
--cc=psexton@xnet.co.nz \
/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).