From owner-freebsd-bugs Tue Apr 2 20:50:10 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id B287537B41F for ; Tue, 2 Apr 2002 20:50:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g334o2E22507; Tue, 2 Apr 2002 20:50:02 -0800 (PST) (envelope-from gnats) Date: Tue, 2 Apr 2002 20:50:02 -0800 (PST) Message-Id: <200204030450.g334o2E22507@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Michael A. Dickerson" Subject: Re: bin/36501: /usr/bin/calendar can't handle recurring items in the next month Reply-To: "Michael A. Dickerson" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR bin/36501; it has been noted by GNATS. From: "Michael A. Dickerson" To: freebsd-gnats-submit@freebsd.org, Cc: Subject: Re: bin/36501: /usr/bin/calendar can't handle recurring items in the next month Date: Tue, 2 Apr 2002 20:47:14 -0800 (PST) Several people have noticed that calendar(1) is brain damaged in a number of ways. Not only does it generate nonsense dates like Mar 32, it seems it can't really process recurring events (first Sunday every month, etc) at all. See bin/34497 from Jan 31 and also bin/4629 from September 1997 (!). I have ported the calendar from OpenBSD, which was rewritten a couple years ago such that it works. The patch is about 60k. However, before you go to the trouble, you might try updating your source and rebuilding. I see somebody made some changes to usr.sbin/calendar on March 12 which might fix your problem. If not I can send you my patch if you like. M.D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message