emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Schedule event
Date: Sat, 06 Aug 2011 17:00:41 +0200	[thread overview]
Message-ID: <807h6qk2jq.fsf@somewhere.org> (raw)
In-Reply-To: C0530846-22AF-4440-AF28-8485C85EC05F@uva.nl

Hi Carsten,

Carsten Dominik wrote:
> On 5.8.2011, at 19:05, Jason Dunsmore wrote:
>> In the Org manual, a distinction is made between items that have a
>> timestamp with the "SCHEDULED" keyword and items that have a plain
>> timestamp:
>> 
>>  "Scheduling an item in Org-mode should not be understood in the same way
>>  that we understand scheduling a meeting. Setting a date for a meeting is
>>  just a simple appointment, you should mark this entry with a simple plain
>>  timestamp, to get this item shown on the date where it applies. This is a
>>  frequent misunderstanding by Org users. In Org-mode, scheduling means
>>  setting a date when you want to start working on an action item."
>> 
>> http://orgmode.org/org.html#Deadlines-and-scheduling
>> 
>> I call these items with plain timestamps "events".

You should add the fact that they're active timestamps in your wording to be
fully accurate -- but I know you do talk about these.

>> These are items that come and go on the agenda whether or not I do
>> anything. I add "events" to my agenda pretty often, so I'd like to schedule
>> them using the same interface I use to schedule SCHEDULED items.
>
> One could certainly combine the code for schedule and deadline into a single
> function and also allow for this function to insert a time stamp without a
> keyword. However, this might lead to confusion. Org internally uses the
> second line in an entry in a special way, for time stamps with keywords like
> DEADLINE, SCHEDULED, CLOSED. It will become confused with time stamps that
> have no keywords.
>
> Why do you want this special interface for setting an event date. How is
> that better than `C-c .'? Is it that you don't need to position the cursor?

I guess so. Even if I'm not really asking for it, I'm sure I'd use such a
function, would it exist.

> Another idea would be to introduce another keyword like APPT an place these
> time stamps also into the second line. That might be more easy to implement.

FWIW, my instinctive reaction would be: yes, great!  Maybe that clarifies the
bits around dates: all active dates get keywords, only inactive ones are
without any keyword.

In that case, I'd opt for EVENT or some such in favor of APPT. Just think at
birthdays, or a TV show: qualifying them as APPT is a bit limitative, IMHO.
EVENT seems a more general term.

Best regards,
  Seb

-- 
Sebastien Vauban

  reply	other threads:[~2011-08-06 15:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-05 17:05 Schedule event Jason Dunsmore
2011-08-06  6:19 ` Carsten Dominik
2011-08-06 15:00   ` Sebastien Vauban [this message]
2011-08-06 18:15     ` suvayu ali
2011-08-06 18:59       ` Sebastien Vauban
2011-08-06 19:42         ` suvayu ali
2011-08-07  6:12           ` Sebastien Vauban
2011-08-06 19:45         ` Jason Dunsmore
2011-08-07  6:14           ` Sebastien Vauban
2011-08-06 19:38     ` Jason Dunsmore
2011-08-07 22:06   ` Jason Dunsmore
2011-08-24 10:26     ` Bastien
2011-08-26 12:08       ` Greg Troxel

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=807h6qk2jq.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).