all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: jorge.a.alfaro@gmail.com (Jorge A. Alfaro-Murillo)
To: emacs-orgmode@gnu.org
Subject: Re: Repeat work / week days
Date: Mon, 09 Jun 2014 12:40:16 -0400	[thread overview]
Message-ID: <878up6f34f.fsf@gmail.com> (raw)
In-Reply-To: 87vbsacb1o.fsf@nicolasgoaziou.fr

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> This is not valid syntax. A given headline cannot have more than one
> SCHEDULED entry attached to it. Even if it works (I didn't test),
> I wouldn't count on it: this is a bug.

I guess if you do not plan to do start working on the task you should
not put the SCHEDULED and just a simple timestamp. But if you plan to
work on a task every day of the week, why shouldn't you be able to do it
this way? It does work, btw. Is it because it can conflict with changing
TODO states?

Also related, if you want it to repeat in your agenda only for a certain
period, look at org-class. For example, while I was a student I had used
things like

#+BEGIN_SRC emacs-lisp
%%(org-class 2013 1 7 2013 4 27 2) 12:00pm-01:15pm The name of the class
%%(org-class 2013 1 7 2013 4 27 4) 12:00pm-01:15pm The name of the class
#+END_SRC

for classes that were Tuesday and Thursday. It was also under a single
headline. Is this, or several simple timestamps under a single headline
also bad syntax?

Best,

Jorge.

  reply	other threads:[~2014-06-09 16:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-09 13:53 Repeat work / week days SabreWolfy
2014-06-09 15:01 ` Jorge A. Alfaro-Murillo
2014-06-09 16:17   ` Nicolas Goaziou
2014-06-09 16:40     ` Jorge A. Alfaro-Murillo [this message]
2014-06-09 16:56       ` Nicolas Goaziou
2014-06-09 17:07         ` Jorge A. Alfaro-Murillo
2014-06-09 16:12 ` Nick Dokos
2014-06-09 16:22   ` Nick Dokos
2014-06-11  9:17     ` SabreWolfy

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878up6f34f.fsf@gmail.com \
    --to=jorge.a.alfaro@gmail.com \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.