emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bernt Hansen <bernt@alumni.uwaterloo.ca>
To: emacs-orgmode@gnu.org
Subject: Re: struggling with fixed date entries
Date: Sun, 26 Aug 2007 21:14:23 -0400	[thread overview]
Message-ID: <87ps19hj80.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: fat6h5$qnb$1@sea.gmane.org

Rainer Stengele <rainer.stengele@diplan.de> writes:

> I wonder what is the best way to work with fixed dates in org.
> I do not want to them entered as "SCHEDULED".
>
> Say I have a meeting on a certain date.
> I do not want to enter it as a todo, as for me it is not really a todo
> but a simple meeting which is done when it is over.
> If I enter it as a simple headline (todo or no todo) and schedule it
> it will show up after the meeting as due until I mark it as "DONE" or
> delete the schedule.
>
> Now I could use the diary. Agenda view will show the event and
> complain no more after it is past. Disadvantage: I cannot org-tag the
> diary entry.
> As I do not use the diary and diary functions are included in org I
> can use something like:
>
>    * Fixed date event                                  :@LOCATION:
>      <%%(diary-date 29 08 2007)>
>
> which is ugly and cannot be entered with the help of the calendar (as
> by "C-c C-s"
>
> What do you think? Would it be a good idea to at least support the
> entering of a "diary-date" by a org function directly with the help of
> the calendar? Maybe create a third type of schedule type: "FIXED"
> besides of "SCHEDULED" and "DEADLINE"?
>
> How do you manage fixed events?

What's wrong with just using a regular date?

* Test Meeting
<2007-08-27 Mon 10:00-11:00>

It shows up on the agenda on the date and time specified similar to a
diary entry.

Bernt

  reply	other threads:[~2007-08-27  1:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-27  0:40 struggling with fixed date entries Rainer Stengele
2007-08-27  1:14 ` Bernt Hansen [this message]
2007-08-27  1:14 ` Bernt Hansen
2007-08-27  8:13   ` Rainer Stengele

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=87ps19hj80.fsf@gollum.intra.norang.ca \
    --to=bernt@alumni.uwaterloo.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).