From: "François Pinard" <pinard@iro.umontreal.ca>
To: emacs-orgmode@gnu.org
Subject: Re: Simplifying the weekly agenda a tiny bit, howto?
Date: Thu, 18 Jul 2013 10:42:41 -0400 [thread overview]
Message-ID: <86txjsylni.fsf@iro.umontreal.ca> (raw)
In-Reply-To: <878v14801v.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Thu, 18 Jul 2013 21:33:48 +0800")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> 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).
How do I get it quickly rescheduled then, when it is a regular activity?
I find fairly convenient using "t d" to push an activity at its next
slot in the future. Could I do something equivalent with mere time
stamps?
> 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 many Org commands able to find, display and otherwise handle
TODOs. If I stop using such keywords, wouldn't I give up the tools?
Maybe there are ways to reformulate them all using other commands, but
at fist, it would require some searching, and acquiring new habits,
presuming that there are alternative ways for all such tools.
> There are a host of variables [...] Check out variables starting
> org-agenda-skip-*, org-agenda-ignore-*, org-agenda-include-*,
> org-deadline-*, org-scheduled-* [...] Hope that helps,
Undoubtedly :-). Thanks!
François
next prev parent reply other threads:[~2013-07-18 14:42 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
2013-07-18 14:42 ` François Pinard [this message]
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=86txjsylni.fsf@iro.umontreal.ca \
--to=pinard@iro.umontreal.ca \
--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).