From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: Simplifying the weekly agenda a tiny bit, howto?
Date: Thu, 18 Jul 2013 21:33:48 +0800 [thread overview]
Message-ID: <878v14801v.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 86y594yqnn.fsf@iro.umontreal.ca
François Pinard <pinard@iro.umontreal.ca> writes:
> Hi, Org friends. Here is an (edited) copy of my weekly agenda:
>
>
> Week-agenda (W29):
> Lundi 15 Juillet 2013 W29
> Mardi 16 Juillet 2013
> Mercredi 17 Juillet 2013
> Jeudi 18 Juillet 2013
> notes: In 1 d.: TODO *Some meeting
> Automobile: In 4 d.: TODO Another thing
> [...]
> Vendredi 19 Juillet 2013
> notes: 20:30...... Deadline: TODO *Some meeting
> Samedi 20 Juillet 2013
> Dimanche 21 Juillet 2013
> [...]
>
>
> The Vendredi (Friday) lines is clearly shown in red (yet in the quote
> above, it is likely shown in black and white!). So the Jeudi (Thursday)
> reference to the same activity is superfluous to me. I wonder if there
> is a (simple) way to inhibit, in a weekly agenda, any announced activity
> which appears later down in the same agenda.
>
> François
First of all, if your event is a meeting, it should only be timestamped,
not deadlined or scheduled. Then it will just show up where it's
supposed to, and not before (or after). It probably shouldn't even be a
TODO.
Otherwise, scheduled TODOs show up on their schedule, and deadlined
TODOs show up on their deadline, and also today's agenda, if you're
coming up on the deadline. There are a host of variables that change how
a TODO is displayed depending on whether it has a
schedule/deadline/timestamp, or one and not the others, or `how close
you are to it, etc. Check out variables starting org-agenda-skip-*,
org-agenda-ignore-*, org-agenda-include-*, org-deadline-*,
org-scheduled-*, there are plenty of ways of screening out TODOs that
you don't want to see until you're supposed to see them.
Hope that helps,
Eric
next prev parent reply other threads:[~2013-07-18 13:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 12:54 Simplifying the weekly agenda a tiny bit, howto? François Pinard
2013-07-18 13:33 ` Eric Abrahamsen [this message]
2013-07-18 14:42 ` François Pinard
2013-07-19 2:19 ` Richard Lawrence
2013-07-19 14:51 ` François Pinard
2013-07-19 8:56 ` Eric Abrahamsen
2013-07-19 14:37 ` François Pinard
2013-07-20 11:34 ` Samuel Loury
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=878v14801v.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).