Return to Answer

You can achieve that using template expansion. As %(EXP) will expand a lisp expression, you can take advantage of it.

Rewriting the template's scheduled part to this will do it

SCHEDULED: %(concat \"<\" (format-time-string \"%Y-%m-%d\") \" +1y\>\")

Surely there is a more general "org-way" to do it if you dig enough into timestamp objects, but I haven't been able to figure how to make it work with org-insert-timestamp as PRE and POST are inserted out of timestamp;

Also, you can use org-insert-timestamp's (stated but undocumented) EXTRA argument to pass it, so:

SCHEDULED: %(org-insert-timestamp nil nil nil nil nil \" +1y\")

will do the same. For more complex date choices than current date probably using org-read-date will help.

You can achieve that using template expansion. As %(EXP) will expand a lisp expression, you can take advantage of it.

Rewriting the template's scheduled part to this will do it

SCHEDULED: %(concat \"<\" (format-time-string \"%Y-%m-%d\") \" +1y\>\")

Surely there is a more general "org-way" to do it if you dig enough into timestamp objects, but I haven't been able to figure how to make it work with org-insert-timestamp as PRE and POST are inserted out of timestamp;

Also, you can use org-insert-time-stamp's (stated but undocumented) EXTRA argument to pass it, so:

SCHEDULED: %(org-insert-time-stamp nil nil nil nil nil \" +1y\")

will do the same. For more complex date choices than current date probably using org-read-date will help.

You can achieve that using template expansion. As %(EXP) will expand a lisp expression, you can take advantage of it.

Rewriting the template's scheduled part to this will do it

SCHEDULED: %(concat \"<\" (format-time-string \"%Y-%m-%d\") \" +1y\>\")

Surely there is a more general "org-way" to do it if you dig enough into timestamp objects, but I haven't been able to figure how to make it work with org-insert-timestamp as PRE and POST are inserted out of timestamp;

Also, you can use org-insert-timestamp's (undocumented) EXTRA argument to pass it, so:

SCHEDULED: %(org-insert-timestamp nil nil nil nil nil \" +1y\")

will do the same. For more complex date choices than current date probably using org-read-date will help.

You can achieve that using template expansion. As %(EXP) will expand a lisp expression, you can take advantage of it.

Rewriting the template's scheduled part to this will do it

SCHEDULED: %(concat \"<\" (format-time-string \"%Y-%m-%d\") \" +1y\>\")

Surely there is a more general "org-way" to do it if you dig enough into timestamp objects, but I haven't been able to figure how to make it work with org-insert-timestamp as PRE and POST are inserted out of timestamp;

Also, you can use org-insert-timestamp's (stated but undocumented) EXTRA argument to pass it, so:

SCHEDULED: %(org-insert-timestamp nil nil nil nil nil \" +1y\")

will do the same. For more complex date choices than current date probably using org-read-date will help.

You can achieve that using template expansion. As %(EXP) will expand a lisp expression, you can take advantage of it.

Rewriting the template's scheduled part to this will do it

SCHEDULED: %(concat \"<\" (format-time-string \"%Y-%m-%d\") \" +1y\>\")

Surely there is a more general "org-way" to do it if you dig enough into timestamp objects, but I haven't been able to figure how to make it work with org-insert-timestamp as PRE and POST are inserted out of timestamp;

Also, you can use org-insert-timestamp's extra Argument to pass it, so

SCHEDULED: %(org-insert-timestamp nil nil nil nil nil \" +1y\")

will do the same. For more complex date choices than current date probably using org-read-date will help.

You can achieve that using template expansion. As %(EXP) will expand a lisp expression, you can take advantage of it.

Rewriting the template's scheduled part to this will do it

SCHEDULED: %(concat \"<\" (format-time-string \"%Y-%m-%d\") \" +1y\>\")

Surely there is a more general "org-way" to do it if you dig enough into timestamp objects, but I haven't been able to figure how to make it work with org-insert-timestamp as PRE and POST are inserted out of timestamp;

Also, you can use org-insert-timestamp's (undocumented) EXTRA argument to pass it, so:

SCHEDULED: %(org-insert-timestamp nil nil nil nil nil \" +1y\")

will do the same. For more complex date choices than current date probably using org-read-date will help.