From mboxrd@z Thu Jan  1 00:00:00 1970
From: Kyle Meyer <kyle@kyleam.com>
Subject: Re: [bug/regression]: org-babel-load-file gives error:
 wrong-type-argument listp "/home/grfz/.emacs.d/configuration.org"
Date: Mon, 14 Jan 2019 17:10:18 -0500
Message-ID: <87y37moppx.fsf@kyleam.com>
References: <20190114171341.evndlhvio4kmgowu@len.workgroup>
	<871s5eq51i.fsf@kyleam.com>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([209.51.188.92]:54070)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kyle@kyleam.com>) id 1gjAR9-0003Ze-6d
	for emacs-orgmode@gnu.org; Mon, 14 Jan 2019 17:10:28 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kyle@kyleam.com>) id 1gjAR7-0004rC-8o
	for emacs-orgmode@gnu.org; Mon, 14 Jan 2019 17:10:27 -0500
Received: from pb-smtp1.pobox.com ([64.147.108.70]:54991)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <kyle@kyleam.com>) id 1gjAR6-0004iE-Sy
	for emacs-orgmode@gnu.org; Mon, 14 Jan 2019 17:10:25 -0500
In-Reply-To: <871s5eq51i.fsf@kyleam.com>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode/>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: "Emacs-orgmode"
	<emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: Gregor Zattler <telegraph@gmx.net>, emacs-orgmode <emacs-orgmode@gnu.org>

Kyle Meyer <kyle@kyleam.com> writes:

> Gregor Zattler <telegraph@gmx.net> writes:

[...]

>> I did a git bisect on the org repo and got this:
>> ba321d0e44b34840466dd386223f702615ff8562 is the first bad commit
>
> Sorry, that certainly looks to be my fault (specifically, my conflict
> resolution merging maint's d64c9a996).  I'll have a look.

Fixed by baa98a4a6fe93dd99fb624ad218fb3e1868cfde3.

-- 
Kyle