Comment 3 for bug 908233

Hi Ivan,
  Hmm this is a bit complicated; there are two things going on - and I'm not sure which cygwin do:

1) bsdmainutils uses an oldschool Unix trick to use the same binary for cal and ncal; it decides what to do based on the name of the binary that it was run as; I'm not sure if cygwin does the same thing or not. Now, if it's run as 'cal' it sets a backwards compatibility flag.

2) The -M option doesn't seem to be in the bsdmainutils by default, but it comes from a patch in the debian package (ncal_mfdow.diff) and it has the code:

+ case 'M':
+ if (flag_backward)
+ usage();
+ weekstart = 1;
+ break;

So the intention there is pretty clear it wants that when in backward compatibility mode it wants to tell you M isn't supported.

So, not sure what cygwin uses.

Dave