emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] Schedule event


From: Carsten Dominik
Subject: Re: [O] Schedule event
Date: Sat, 6 Aug 2011 08:19:56 +0200

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".  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.
> 
> Someone on IRC suggested that I use the following function:
> 
> --8<---------------cut here---------------start------------->8---
> (defun org-schedule-event ()
>  (interactive)
>  (let ((org-scheduled-string ""))
>    (org-schedule)))
> --8<---------------cut here---------------end--------------->8---
> 
> However, it inserts an extra space.  Example:
> 
> --8<---------------cut here---------------start------------->8---
> * Test
>   <2011-08-05 Fri>
> --8<---------------cut here---------------end--------------->8---
> 
> instead of:
> 
> --8<---------------cut here---------------start------------->8---
> * Test
>  <2011-08-05 Fri>
> --8<---------------cut here---------------end--------------->8---
> 
> I could hack together a fix for this, but I was thinking that perhaps
> the org-schedule function should be made more general so that it can be
> combined with the org-deadline function, which has much of the same
> code, and used to insert plain timestamps as well.  Thoughts?

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?

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.



> 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]