From: Jason Dunsmore <emacs-orgmode@dunsmor.com>
To: emacs-orgmode@gnu.org, dominik@uva.nl, bzg@altern.org
Subject: Schedule event
Date: Fri, 05 Aug 2011 12:05:23 -0500 [thread overview]
Message-ID: <877h6raiwc.fsf@riotblast.dunsmor.com> (raw)
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?
next reply other threads:[~2011-08-05 17:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 17:05 Jason Dunsmore [this message]
2011-08-06 6:19 ` Schedule event Carsten Dominik
2011-08-06 15:00 ` Sebastien Vauban
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=877h6raiwc.fsf@riotblast.dunsmor.com \
--to=emacs-orgmode@dunsmor.com \
--cc=bzg@altern.org \
--cc=dominik@uva.nl \
--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).