From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Davis Subject: Re: Org now failing on HTML export Date: Fri, 30 Jun 2017 15:00:39 -0400 Message-ID: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44807) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dR19o-0002XT-S1 for emacs-orgmode@gnu.org; Fri, 30 Jun 2017 15:00:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dR19l-0005NN-PZ for emacs-orgmode@gnu.org; Fri, 30 Jun 2017 15:00:44 -0400 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:34707) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dR19l-0005Mn-Ij for emacs-orgmode@gnu.org; Fri, 30 Jun 2017 15:00:41 -0400 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" To: Kaushal Modi Cc: emacs-orgmode@gnu.org Kaushal Modi writes: > On Fri, Jun 30, 2017 at 2:07 PM Peter Davis wrote: > > I've been using org 9.0.7/GNU Emacs 25.1.1 on Mac OS X for a while, and successfully exporting HTML to copy and paste into my blog. > However, in the last day or so, this started failing. I'm unaware of having changed anything in my configuration. > > The error is ... > > Here's the entire file I'm using ... > > +============ > Does this work at all? > +============ > > Here's the debug traceback ... > > +============ > Debugger entered--Lisp error: (wrong-type-argument listp #("org test" 0 8 (:parent (#1)))) > > You have the classic case of mixed Org installations, would be my guess. > > I haven't seen this issue myself but it's a well-known issue with mixed Org installations. > > Best way that I have seen to work is to delete (M)Elpa installed Org completely and install it again, but in an emacs -Q session, or do C-u M-x org-reload, and then delete->reinstall Org. Aha! I think you've hit the nail on the head. I'm not sure how this happened, but org-reload does seem to correct the problem. Thank you, Kaushal! -pd