From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: error on org-reload (Symbol's value as variable is void: load-uncore) Date: Fri, 11 Mar 2016 10:43:01 -0500 Message-ID: <87wpp910my.fsf@pierrot.dokosmarshall.org> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36250) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aePDl-00024o-5M for emacs-orgmode@gnu.org; Fri, 11 Mar 2016 10:43:22 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aePDh-0003la-5i for emacs-orgmode@gnu.org; Fri, 11 Mar 2016 10:43:21 -0500 Received: from plane.gmane.org ([80.91.229.3]:44772) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aePDg-0003lT-Vc for emacs-orgmode@gnu.org; Fri, 11 Mar 2016 10:43:17 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1aePDe-0007jM-0k for emacs-orgmode@gnu.org; Fri, 11 Mar 2016 16:43:14 +0100 Received: from pool-74-104-158-160.bstnma.fios.verizon.net ([74.104.158.160]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 11 Mar 2016 16:43:13 +0100 Received: from ndokos by pool-74-104-158-160.bstnma.fios.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 11 Mar 2016 16:43:13 +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 Giuseppe Lipari writes: > Hello, > > I want to have a backtrace of an error I am encountering. So I followed the instructions here, > 1) I enabled "enter debugger on error" > 2) M-x org-reload > > And I obtain the following error > > and: Symbol's value as variable is void: load-uncore > I think it's time to kill the running emacs session and start a new one. If it happens with the new one, that might be a bug; but IMO it's more likely that the session has been curdled. -- Nick