all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Sam Auciello <olleicua@gmail.com>
To: Sam Auciello <olleicua@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Question about repeating events.
Date: Fri, 13 Jan 2012 10:41:17 -0500	[thread overview]
Message-ID: <CAGXuZ6upXbHAQqYN4Fo0Er1O5Mc7wQMk7TtBQuG2kdFhJWHJZA@mail.gmail.com> (raw)
In-Reply-To: <87lipbbotf.fsf@ucl.ac.uk>

[-- Attachment #1: Type: text/plain, Size: 3062 bytes --]

Thanks, I was confused by the distinction between scheduled items and
appointments but you've cleared this up.  What I was thinking would be
cluttered was if I just used the <.. +1w> syntax and I was looking at my
agenda for next semester (when the class is over) then the agenda would be
cluttered with events that weren't meant to be there.  This link:
http://orgmode.org/worg/org-faq.html#org-class, looks to be just what I
needed.

Thanks,

Peace
~Sam

On Fri, Jan 13, 2012 at 10:32 AM, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:

> Sam Auciello <olleicua@gmail.com> writes:
>
> > I apologize in advance if this is the wrong forum for this question.
>
> Not at all; definitely the right place.  However, I would suggest you
> search the mailing list first before asking as your question has come up
> umpteen times before!  It's also answered on Worg.
>
> > I'm trying to set up repeating events to stop repeating after a given
> > date.  In this case it's classes I'm taking this semester that need to
> > repeat once a week so I enter them like:
> >
> > *** Programming Workshop
> >      <2012-01-24 Tue 13:30-14:50 +1w>, <2012-01-20 Fri 13:30-14:50 +1w>
> >
> > The agenda shows the class being scheduled each tuesday and friday but I
> > would like to tell it to stop repeating at the end of the semester.
> >
> > I didn't see anything helpful here:
> > http://orgmode.org/manual/Repeated-tasks.html#Repeated-tasks
> >
> > The options I see here are using C-c C-x c to make a bunch of duplicate
> > entries (which seems a little messy to me, but perhaps this is just how
> > it's done) or simply marking the item as DONE at the end of the semester.
> > The latter option seems a little weird to me too since it would make my
> > agenda for the following semester cluttered if I was looking at it to
> plan
> > future events.  Is there an option I'm overlooking?
> >
> > Thank you,
> >
> > Peace
> > ~Sam
>
> I do the latter (copy with time shift) and have been doing so for quite
> a while.  I find this is quite appropriate for schedules like this as it
> allows one to "miss" the odd entry (e.g. study/reading week or class
> cancelled for whatever reason).
>
> I am not sure what you mean by saying that it makes the agenda
> cluttered?  The result is the same in the agenda view: an entry for each
> day/time a class is scheduled.  I also do not understand your reference
> to marking anything done!  This is not a TODO item, it is an
> appointment.
>
> I think it's worthwhile distinguishing between appointments (which
> *have* to take place at the appointed time) and scheduled work (i.e. a
> /task/ which you intend to do at a certain time but which may end up
> being done earlier or later).  The latter is a TODO item; the former is
> not.  The latter will remain in the agenda view until it is marked done
> whereas the former only appears on the time+day indicated.
>
> I hope this makes some sort of sense...
>
> --
> : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.92.1
> : using Org-mode version 7.8.03 (release_7.8.03.122.g5b407)
>

[-- Attachment #2: Type: text/html, Size: 3934 bytes --]

      reply	other threads:[~2012-01-13 15:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-12 16:13 Question about repeating events Sam Auciello
2012-01-13 15:12 ` Brian Wightman
2012-01-13 15:41   ` Nick Dokos
2012-01-13 15:32 ` Eric S Fraga
2012-01-13 15:41   ` Sam Auciello [this message]

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=CAGXuZ6upXbHAQqYN4Fo0Er1O5Mc7wQMk7TtBQuG2kdFhJWHJZA@mail.gmail.com \
    --to=olleicua@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.