emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Greg Novak" <novak@ucolick.org>
To: emacs-orgmode@gnu.org
Subject: Obliterating schedule/deadline repeaters
Date: Fri, 13 Jun 2008 17:24:01 -0700	[thread overview]
Message-ID: <ad0d4fcf0806131724i70d5b79l62273291bb3d24@mail.gmail.com> (raw)

On the whole I'm happily using org-mode.  One thing that I'm unhappy
with is that when I'm looking at the agenda and decide to reschedule a
task that has a repeater, the repeater is obliterated.  That is, if
the task is:

* TODO Oil change
  SCHEDULED <2008-6-1 +3m>

and I think to myself "I'll do that on Saturday, not on Tuesday" then
hit C-c C-s and put in the new date, the repeater is obliterated.
Ideally, the repeater would just be preserved as-is.  Almost as good
is if there's some clue in the minibuffer that the task has a repeater
and I should remember to include it in the new date.  As it stands, I
have this in my .emacs file to prevent manual changes to tasks with
repeaters---in that case I just look at the org file and change the
schedule date manually:

(defadvice org-schedule
  (around gsn/org-prevent-rescheduling-repeated-tasks activate)
  "If the current task has a repeater, prevent rescheduling it to
avoid obliterating the repeater."
  (if (org-get-repeat)
      (message "*** Can't reschedule this task without obliterating
repeater ***")
      ad-do-it))

I'm writing the list to see if there's a way to do this and I was just
dumb when I read the manual.  If not, I guess this is a feature
request.  I'm using v 6.04c.

Best,
Greg

             reply	other threads:[~2008-06-14  0:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-14  0:24 Greg Novak [this message]
2008-06-16 16:16 ` Obliterating schedule/deadline repeaters Carsten Dominik

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=ad0d4fcf0806131724i70d5b79l62273291bb3d24@mail.gmail.com \
    --to=novak@ucolick.org \
    --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).