A similar request just made its way to palcal-devel. Here
is an update on what I'm thinking about this:
Bi-weekly is needed for sure. It would be nice to figure
out a way to
implement it so that it extends to other events (bi-monthly,
bi-daily). Anyway, we just need to come up with a clever way to
express it in the file format---that is the main thing that
is holding
me back on this right now.
Suggestions are welcome.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Possibly something like:
R<num><day>
for bi/tri weekly, where <num> = (for example) 2 for bi and
3 for tri, and <day> is the day of the week it would appear on.
e.g. to repeat every other friday: B2fri
For bi/tri monthly and bi/tri daily, something like:
R<num><type><startdate>
where <num> = (for example) 2 for bi, and 3 for tri, <type>
= D for day, M for month, Y for year, and <startdate> would
be the date that it would start from.
e.g. to repeat every other day starting on march first:
B2D20040301
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This doesn't quite work because we need to have a start
date. This format could be used to say "every other
tuesday" but it doesn't tell us which tuesday we start from.
So we need what you called <startday> in whatever format we
use.
Besides that, I think the previous comment is on the right
track.
I think something like the following would have the least
impact on the current file format:
- Require startDate and endDate
- Use this format:
eventType:startDate:endDateRN
where N >= 2; 2=bi-eventType, 3=tri-eventType, etc.
For example, if eventType is "last friday in June", we look
for the first "last friday in June" after startDate. Then,
we use N to determine if every following "last friday in
June" has the event on it (up until endDate).
I think this particular format would cover all possibilities
and wouldn't impact the pal calendar file format much.
Any comments?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If anyone found this discussion because they are trying to figure out how to set up a bi-weekly event in pal, this is how got it to work:
EX: a meeting @ 11am every other Thursday, the date structure (formatting?) would look like this:
THU/2:startDate:endDate
Substitute the date with any of pal's date commands to suit (SUN,MON,TUE,WED,THU,FRI,SAT)
I do not think this is possible when in pal, but I use this command in my terminal to add it to my calendar:
The pal man page gives an example for bi-monthly that didn't really help with this sort of even scheduling. Hopefully this helps someone else trying to set up bi-weekly events.
Last edit: richard 2021-01-12
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=941561
I agree this is a good idea. I'll see if I can get
something implemented before the next release.
Logged In: YES
user_id=941561
A similar request just made its way to palcal-devel. Here
is an update on what I'm thinking about this:
Bi-weekly is needed for sure. It would be nice to figure
out a way to
implement it so that it extends to other events (bi-monthly,
bi-daily). Anyway, we just need to come up with a clever way to
express it in the file format---that is the main thing that
is holding
me back on this right now.
Suggestions are welcome.
Logged In: YES
user_id=941561
Also, it would be nice if we find a file format that would
extend to tri-weekly, etc.
Logged In: YES
user_id=358399
Possibly something like:
R<num><day>
for bi/tri weekly, where <num> = (for example) 2 for bi and
3 for tri, and <day> is the day of the week it would appear on.
e.g. to repeat every other friday: B2fri
For bi/tri monthly and bi/tri daily, something like:
R<num><type><startdate>
where <num> = (for example) 2 for bi, and 3 for tri, <type>
= D for day, M for month, Y for year, and <startdate> would
be the date that it would start from.
e.g. to repeat every other day starting on march first:
B2D20040301
Logged In: YES
user_id=941561
>Possibly something like:
>R<num><day>
This doesn't quite work because we need to have a start
date. This format could be used to say "every other
tuesday" but it doesn't tell us which tuesday we start from.
So we need what you called <startday> in whatever format we
use.
Besides that, I think the previous comment is on the right
track.
I think something like the following would have the least
impact on the current file format:
- Require startDate and endDate
- Use this format:
eventType:startDate:endDateRN
where N >= 2; 2=bi-eventType, 3=tri-eventType, etc.
For example, if eventType is "last friday in June", we look
for the first "last friday in June" after startDate. Then,
we use N to determine if every following "last friday in
June" has the event on it (up until endDate).
I think this particular format would cover all possibilities
and wouldn't impact the pal calendar file format much.
Any comments?
If anyone found this discussion because they are trying to figure out how to set up a bi-weekly event in pal, this is how got it to work:
EX: a meeting @ 11am every other Thursday, the date structure (formatting?) would look like this:
THU/2:startDate:endDate
Substitute the date with any of pal's date commands to suit (SUN,MON,TUE,WED,THU,FRI,SAT)
I do not think this is possible when in pal, but I use this command in my terminal to add it to my calendar:
$ echo 'date-details pal-event-description' >> /path/to/pal/cal.pal
The pal man page gives an example for bi-monthly that didn't really help with this sort of even scheduling. Hopefully this helps someone else trying to set up bi-weekly events.
Last edit: richard 2021-01-12