I can confirm that neither ranges (ie. "11,16") nor lists (ie. "1-5")
are currently parsed:
$ perl -d -Ilib -MPegex::Crontab \
-e '$crontab = Pegex::Crontab->new->parse(' \
-e ' "30 11,16 * * 1-5 tar -zcf /var/backups/home.tgz /home/" . "\n"' \
-e ');' \
Error parsing Pegex document:
msg: Parse document failed for some reason
line: 1
column: 6
context: 30 11,16 * * 1-5 tar -zcf /var/backups/home.tgz /home/\n
^
position: 5 (0 pre-lookahead)
at /home/tommy.stanton/perl5/lib/perl5/Pegex/Module.pm line 27.
$ perl -d -Ilib -MPegex::Crontab \
-e '$crontab = Pegex::Crontab->new->parse(' \
-e ' "30 11 * * 1-5 tar -zcf /var/backups/home.tgz /home/" . "\n"' \
-e ');' \
Error parsing Pegex document:
msg: Parse document failed for some reason
line: 1
column: 12
context: 30 11 * * 1-5 tar -zcf /var/backups/home.tgz /home/\n
^
position: 11 (0 pre-lookahead)
at /home/tommy.stanton/perl5/lib/perl5/Pegex/Module.pm line 27.
On Thu Nov 08 18:18:51 2012, SHARYANTO wrote:
Show quoted text> 1. Environment setting line should allow whitespace around the
> variable, e.g.:
>
> FOO = val
> BAR= val
>
> 2. Allow lists in the time/date fields, e.g.:
>
> 0 1 1,2,3 * * cmd
>
> 3. Allow step value in time/date fields, e.g.:
>
> */5 * * * * cmd
>
> Note that cron also allows lists of stepped values, e.g.:
>
> */5,59 * * * * cmd
>
> 4. Allow month name (Jan) and day of week name (Sun).
