From: Nick Dokos <firstname.lastname@example.org>
Subject: Re: a repeater doesn't increment
Date: Thu, 22 Jul 2021 17:12:20 -0400 [thread overview]
Message-ID: <email@example.com> (raw)
Jude DaShiell <firstname.lastname@example.org> 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 may be misunderstanding, but are you trying to fill a column in a table
with dates that are four weeks apart? If so, repeaters have nothing to do
with it (AFAIK). You need `org-table-copy-increment' to be set to 28.
| date | foo |
| <2021-07-22 Thu> | |
| <2021-08-19 Thu> | |
| <2021-09-16 Thu> | |
| <2021-10-14 Thu> | |
| <2021-11-11 Thu> | |
| <2021-12-09 Thu> | |
(setq-local org-table-copy-increment 28)
Then keep pressing `S-RET' to get the next date.
> On Tue, 20 Jul 2021, Jude DaShiell wrote:
>> 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
>> What am I doing wrong?
"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler
next prev parent reply other threads:[~2021-07-22 21:13 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 [this message]
2021-07-23 3:08 ` Jude DaShiell
2021-07-27 15:57 ` Nick Dokos
2021-07-27 16:55 ` Jude DaShiell
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 \
* 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).