Jorey Bump | 5 Jan 15:08 2009

Incorrect Dates for February 2009

While reviewing the web calendar I generate with remind, I noticed that
 it shows February 2009 beginning on a Monday and ending on a Sunday
(overlapping the first day of March). February 2009 actually begins on a
Sunday and ends on a Saturday. January is correct, and so is March and
the following months.

I get the same results from versions 03.01.03 and 03.01.06.

Jorey Bump | 5 Jan 15:19 2009

Re: Incorrect Dates for February 2009

Jorey Bump wrote, at 01/05/2009 09:08 AM:
> While reviewing the web calendar I generate with remind, I noticed that
>  it shows February 2009 beginning on a Monday and ending on a Sunday
> (overlapping the first day of March). February 2009 actually begins on a
> Sunday and ends on a Saturday. January is correct, and so is March and
> the following months.
> 
> I get the same results from versions 03.01.03 and 03.01.06.

Update: The output using -c+10 displays the correct dates in the
terminal, so it must be a problem with my heavily customized rem2html
script.

David F. Skoll | 5 Jan 15:27 2009

Re: Incorrect Dates for February 2009

Jorey Bump wrote:

> While reviewing the web calendar I generate with remind, I noticed that
>  it shows February 2009 beginning on a Monday and ending on a Sunday
> (overlapping the first day of March). February 2009 actually begins on a
> Sunday and ends on a Saturday. January is correct, and so is March and
> the following months.

rem2html has been completely rewritten; please try the latest version
from 03.01.06.  From the release notes for 03.01.04:

- BUG FIX: rem2html would output a horribly-wrong calendar for a 28-day
  February starting on Sunday (such as February 2009.)  This has been fixed.

Regards,

David.

Jorey Bump | 5 Jan 15:48 2009

Re: Incorrect Dates for February 2009

David F. Skoll wrote, at 01/05/2009 09:27 AM:
> 
> rem2html has been completely rewritten; please try the latest version
> from 03.01.06.  From the release notes for 03.01.04:
> 
> - BUG FIX: rem2html would output a horribly-wrong calendar for a 28-day
>   February starting on Sunday (such as February 2009.)  This has been fixed.

Terrific, that fixed it. Thanks.

Tarlika Elisabeth Schmitz | 6 Jan 23:21 2009
Picon

UK Christmas bank holidays

I have created a list of OMITs for UK bank holidays. However, Christmas
is a bit tricky.

We always get 2 bank holidays regardless on which day Christmas falls:
- If Christmas Day falls on a Friday, Friday and Monday will be bank
holidays.
- If Christmas Day falls on a Saturday, Monday and Tuesday will be bank
holidays.
- If Christmas Day falls on a Monday to Thursday, the bank holidays
will be on Christmas Day and Boxing Day respectively.

How can the OMITs be expressed?

--

Best Regards,

Tarlika Elisabeth Schmitz

Tarlika Elisabeth Schmitz | 7 Jan 00:57 2009
Picon

Re: UK Christmas bank holidays

On Tue, 6 Jan 2009 22:21:58 +0000
Tarlika Elisabeth Schmitz <remind@...> wrote:

> I have created a list of OMITs for UK bank holidays. However,
> Christmas is a bit tricky.
> 
> We always get 2 bank holidays regardless on which day Christmas falls:
> - If Christmas Day falls on a Friday, Friday and Monday will be bank
> holidays.
> - If Christmas Day falls on a Saturday, Monday and Tuesday will be
> bank holidays.
> - If Christmas Day falls on a Monday to Thursday, the bank holidays
> will be on Christmas Day and Boxing Day respectively.
> 
> How can the OMITs be expressed?

For Christmas Day, I figured the following:

REM Mon Tue Wed Thu Fri 25 Dec SCAN [trigger(today()-8)] SATISFY 1
OMIT trigger(trigdate())

--

Best Regards,

Tarlika Elisabeth Schmitz

David F. Skoll | 7 Jan 03:53 2009

Re: UK Christmas bank holidays

Tarlika Elisabeth Schmitz wrote:

> We always get 2 bank holidays regardless on which day Christmas falls:

[...]

So, if Christmas falls on a weekday, you get that day off plus the
next weekday.  And if it falls on a weekend, you get the following
Monday and Tuesday off.  Correct?  So... this should work:

#========================================================================
REM 25 Dec SCANFROM [trigger(today()-7)] OMIT SAT SUN AFTER SATISFY 1
OMIT [trigger(trigdate())] MSG Christmas Bank Holiday

REM 26 Dec SCANFROM [trigger(today()-7)] OMIT SAT SUN AFTER SATISFY 1
OMIT [trigger(trigdate())] MSG Boxing Day Bank Holiday
#========================================================================

Be careful... they have to appear in exactly that order, because if
Christmas falls on a weekend, then the first OMIT sets the stage for
the Boxing Day bank holiday moving to the Tuesday.  Yes, it's tricky...

Regards,

David.

Rainer Clasen | 7 Jan 10:20 2009
Picon

"too many full OMITs"???

Hello,

for scheduling my private activities I have a recurring entry for "work"
and a bunch of OMIT's for each day I've vacation (BTW: unfortunatly ranges
don't seem to work with OMIT):

 PUSH
  OMIT May 22 2009 MSG vacation
  [...other vacation days...]
  REM mon thu wed tue fri SKIP AT 8:00 DURATION 9:00 CAL work
 POP

But when I entered this years schedul I got:

 warp:~$ grep OMIT ~/.reminders | wc -l
 112
 warp:~$ remind -q
 /home/bj/.reminders(199): Too many full OMITs

So I'm in need of an alternative or a fix. 

FYI: It's remind version 03.00.24 (as included in debian etch) I'm using.

Rainer

--

-- 
KeyID=759975BD fingerprint=887A 4BE3 6AB7 EE3C 4AE0  B0E1 0556 E25A 7599 75BD

David F. Skoll | 7 Jan 13:03 2009

Re: "too many full OMITs"???

Rainer Clasen wrote:

> for scheduling my private activities I have a recurring entry for "work"
> and a bunch of OMIT's for each day I've vacation (BTW: unfortunatly ranges
> don't seem to work with OMIT):

I'd recommend upgrading to Remind 3.1.6 and rewriting your reminders
to use computed OMITs.  Or, you can recompile Remind to increase
MAX_FULL_OMITS.  (In fact, I believe 3.1.6 increases it from 75 to 250,
which might be all you need.)

Regards,

David.

Rainer Clasen | 7 Jan 15:45 2009
Picon

Re: "too many full OMITs"???

David F. Skoll wrote:
> Rainer Clasen wrote:
> 
> > for scheduling my private activities I have a recurring entry for "work"
> > and a bunch of OMIT's for each day I've vacation (BTW: unfortunatly ranges
> > don't seem to work with OMIT):
> 
> I'd recommend upgrading to Remind 3.1.6 and rewriting your reminders
> to use computed OMITs.  Or, you can recompile Remind to increase
> MAX_FULL_OMITS.  (In fact, I believe 3.1.6 increases it from 75 to 250,
> which might be all you need.)

Thanks for your hint. Looking at OMITFUNC I've been remembered of SATISFIY
(which is sufficient for this case):

 FSET between(x,a,b)     (x>=a && x <=b)

 FSET vacation_2009(x) ( 0 \
        || between(x, '2009-3-6', '2009-3-23' )\
        || between(x, '2009-7-30', '2009-8-2' )\
        )

 FSET vacation(x) ( vacation_2009(x) || vacation_2008(x))
 REM SATISFY [ vacation(today()) ] MSG vacation
 REM mon thu wed tue fri SKIP \
        AT 8:00 DURATION 9:00 \
        SATISFY [!vacation(today())] \
        CAL work

Oh, yeah, removing last year's stuff was too easy ;)
(Continue reading)


Gmane