emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: a repeater doesn't increment
Date: Tue, 27 Jul 2021 11:57:16 -0400	[thread overview]
Message-ID: <87sfzzu4v7.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: alpine.NEB.2.23.451.2107222307190.14236@panix1.panix.com

Jude DaShiell <jdashiel@panix.com> writes:

> What I'm trying to do is more complex than that.
> * Reorder pills
> ** TODO order hctz, lisinipril, metformin, provacol, claritin, Co-q10,
>    Deadline: <8-2-2021 +4w>
> ** TODO order Colase
>    Deadline: <10-13-2021 +14w>
> ** TODO order Turmerick
>    Deadline: <8-30-2021 +8w>
> On Thu, 22 Jul 2021, Nick Dokos wrote:
>> Jude DaShiell <jdashiel@panix.com> writes:
>> > Does enough material exist on werg tutorials that document how to get a
>> > repeater operational?  That or maybe I don't understand repeaters.  Had
>> > the repeater I tried to use worked correctly it would have advanced the
>> > original date by 4 weeks when that date got copied down to another cell.
>> > I selected the whole line including both verticals and perhaps this works
>> > when only a time stamp is copied.
>> >
>> >> I am likely doing this wrong but will describe what has been done.
>> >> I put an agenda time stamp into a field in test.org and add +4w to the end
>> >> of the time stamp inside the >.
>> >> I get on the left of the field column on the vertical character and type
>> >> control-space to set mark.
>> >> I move to the end of the field on the > sign and type space and another
>> >> vertical to close the column entry for that field.
>> >> Next I do control-c+x+v and am told strings are copied to the kill ring.
>> >> Next I move down one line and type control-y to yank those strings out of
>> >> the kill buffer and paste them on that line.
>> >> When this is done, I expected the time stamp to increment by 4 weeks.
>> >> What happened was the same information got copied down and it didn't
>> >> increment.
>> >> What am I doing wrong?
>> >>

I still don't understand: in your most recent response (at the top of this thread)
you are talking about headlines with DEADLINE added (which seems the right approach
to me: is there a problem with it?) But in your original mail, as well as in the followup, you are
taling about "field columns" and "vertical characters" and "cop[ying] down to another cell",
which seems to imply that you have an Org mode table somewhere.

Maybe you can elaborate a bit?

"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler

  reply	other threads:[~2021-07-27 15:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-20 19:41 a repeater doesn't increment Jude DaShiell
2021-07-22  1:47 ` Jude DaShiell
2021-07-22  8:49   ` Henrik Frisk
2021-07-22 12:36     ` Jude DaShiell
2021-07-22 21:12   ` Nick Dokos
2021-07-23  3:08     ` Jude DaShiell
2021-07-27 15:57       ` Nick Dokos [this message]
2021-07-27 16:55         ` Jude DaShiell

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:

  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=87sfzzu4v7.fsf@alphaville.usersys.redhat.com \
    --to=ndokos@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).