From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: [PATCH] Avoid lisp error with (org-deadline nil "+1d") Date: Wed, 23 Nov 2011 18:21:57 -0500 Message-ID: <5331.1322090517@alphaville.dokosmarshall.org> References: <871ut1hzh0.fsf@micropit.couberia.bzh> <878vn73j7o.fsf@micropit.couberia.bzh> <040C8B85-F131-4FE1-ABCF-AB368CF42C5A@gmail.com> <87obw2wo5g.fsf@micropit.couberia.bzh> <1945.1322082831@alphaville.dokosmarshall.org> <87aa7mwjsd.fsf@micropit.couberia.bzh> Reply-To: nicholas.dokos@hp.com Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([140.186.70.92]:58454) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RTM8f-0002MI-EA for emacs-orgmode@gnu.org; Wed, 23 Nov 2011 18:22:02 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RTM8e-00044e-B0 for emacs-orgmode@gnu.org; Wed, 23 Nov 2011 18:22:01 -0500 Received: from g6t0185.atlanta.hp.com ([15.193.32.62]:38877) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RTM8e-00044H-1z for emacs-orgmode@gnu.org; Wed, 23 Nov 2011 18:22:00 -0500 In-Reply-To: Message from pmlists@free.fr (Peter =?us-ascii?Q?=3D=3Futf-8?= =?us-ascii?Q?=3FQ=3FM=3DC3=3DBCnster=3F=3D?=) of "Wed\, 23 Nov 2011 23\:33\:54 +0100." <87aa7mwjsd.fsf@micropit.couberia.bzh> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Peter =?us-ascii?Q?=3D=3Futf-8=3FQ=3FM=3DC3=3DBCnster?= =?us-ascii?Q?=3F=3D?= Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org Peter M=C3=BCnster wrote: > On Wed, Nov 23 2011, Nick Dokos wrote: >=20 > > Generally speaking, defvars like this tell the compiler to shut up about > > the "free" variable. You can see if it is needed, by commenting out the > > defvar and then trying to compile the file. >=20 > Indeed, now there are 30 warnings instead of only 29 ... ;) > Thanks for the explanation! >=20 Are they free variable warnings? If so, you now know how to fix them: go wild :-) Nick