From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: Error when changing todo-state [7.8.11] Date: Wed, 20 Jun 2012 13:59:14 -0400 Message-ID: <2919.1340215154@alphaville> References: <20449.31411.363564.346834@lappland.efeu> <87boke6mbs.fsf@ucl.ac.uk> Reply-To: nicholas.dokos@hp.com Return-path: Received: from eggs.gnu.org ([208.118.235.92]:43845) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ShPBi-0007Ml-KI for emacs-orgmode@gnu.org; Wed, 20 Jun 2012 13:59:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ShPBg-0007ED-MC for emacs-orgmode@gnu.org; Wed, 20 Jun 2012 13:59:30 -0400 Received: from g1t0027.austin.hp.com ([15.216.28.34]:14041) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ShPBg-0007E2-HG for emacs-orgmode@gnu.org; Wed, 20 Jun 2012 13:59:28 -0400 In-Reply-To: Message from Eric S Fraga of "Wed, 20 Jun 2012 16:21:27 BST." <87boke6mbs.fsf@ucl.ac.uk> 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: salome.soedergran@gmx.ch, emacs-orgmode@gnu.org Eric S Fraga wrote: > writes: > > > Hi! > > > > I recently upgraded to emacs24 and org 7.8.11. Since this upgrade, > > when I set or change a todo-state, I get an error message > > (void-variable state). The desired todo-state is being set all the > > same. I guess there's some kind of conflict between my config and the > > new org-version -- but what is it and what can I do about it? > > Please find the backtrace and parts of my init-file below. > > "state" has been changed to "org-state". That's probably the cause of the problem, but there is still the question of whether "state" is used in some customization that the OP has done or whether there are inconsistencies in the update (i.e. old bits lying around and being used in preference to the new ones). If tne cure is not obvious given the hints that various people have given, I would suggest M-x toggle-debug-on-error and posting the backtrace. Nick