315475 - support variable interpolation in event names, notes, etc.

Status: RESOLVED DUPLICATE of bug 165298

(Calendar :: General, enhancement)

Description

[Miguel]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051025 Firefox/1.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051025 Firefox/1.5

On a first and possibly easy step, an incremetal variable would be allowed in recurrent event names. The user only would need to insert the starting number, and  the event number would increase by one on every recurrence.

However this concept can be upgraded in very powerfull ways, where only the imagination and utility is the limit. From very simple arithmetic calculations to scripts.

Reproducible: Always




It's common that recurrent events are numbered. For example, if there's a meeting every week at the same day of the week, about the same subject, it would be called meeting 1, meeting 2, ...
At the moment such a meeting can be inserted, but for instance if then someone wants the calendar to send an email to the meeting atendees, it would be nice to have the meeting fully identified.
Another possibility is to have a task that is done every week, but where the user wants to know to what week such a task belongs. Again being able to somehow identify it through a variable would be the solution.

Comment 1

[gekacheka]

(Also note there would need to be an option of whether numbering started from 1 [for meetings, payments] or from 0 [for bithdays and other anniversaries].)

The basic purpose sounds the same as in bug 165298. Marking duplicate.

*** This bug has been marked as a duplicate of 165298 ***

Comment 2

[Dan Mosedale (:dmosedale, :dmose)]

This isn't really a DUP.  While this particular use case is similar to bug 165298, general support for variable interpolation would be significantly more powerful than that.

Comment 3

[Dan Mosedale (:dmosedale, :dmose)]

On closer reading, I was wrong.  This is a DUP; sorry for the spam.

*** This bug has been marked as a duplicate of 165298 ***