From mboxrd@z Thu Jan 1 00:00:00 1970 From: d.tchin Subject: Re: [bug] alias for list-diary-entries-hook creates loop in emacs 24 Date: Wed, 11 Jan 2012 09:41:11 +0000 (UTC) Message-ID: References: <874nw262hz.fsf@ucl.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([140.186.70.92]:46943) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rkugi-0001Vo-UT for emacs-orgmode@gnu.org; Wed, 11 Jan 2012 04:41:46 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RkugZ-0002Mz-66 for emacs-orgmode@gnu.org; Wed, 11 Jan 2012 04:41:44 -0500 Received: from lo.gmane.org ([80.91.229.12]:36930) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RkugY-0002Mt-Tk for emacs-orgmode@gnu.org; Wed, 11 Jan 2012 04:41:35 -0500 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1RkugX-0007HU-Qe for emacs-orgmode@gnu.org; Wed, 11 Jan 2012 10:41:33 +0100 Received: from APuteaux-651-1-185-198.w92-154.abo.wanadoo.fr ([92.154.88.198]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 11 Jan 2012 10:41:33 +0100 Received: from d.tchin by APuteaux-651-1-185-198.w92-154.abo.wanadoo.fr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 11 Jan 2012 10:41:33 +0100 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: emacs-orgmode@gnu.org Eric S Fraga ucl.ac.uk> writes: > > Hello, > > one of the recent updates > > commit d6e40fb3472761ed51795f54491b969976167116 > > to org has caused a problem with the latest emacs snapshot (version from > 5 January I believe). Specifically, the alias for > list-diary-entries-hook would appear to create an alias loop as > diary-lib.el in emacs already has an alias. > > Removing two lines from org-agenda.el (patch attached) fixes the problem > (for me). I am not suggesting this as a patch as it would appear that > an emacs version specific check should probably be made? I don't know > enough about this to suggest a proper solution unfortunately. > > thanks, > eric > I think this bug is related to the correction of a bug I recently submitted related to emacs 22.3. Please follow the link below : http://article.gmane.org/gmane.emacs.orgmode/50960 Hope that can make help. Regards