From mboxrd@z Thu Jan  1 00:00:00 1970
From: Rainer Stengele <rainer.stengele@online.de>
Subject: Re: [BUG] org-agenda-list
Date: Thu, 11 Jul 2013 11:58:14 +0200
Message-ID: <51DE81B6.8000905@online.de>
References: <87d2qp6d23.fsf@gmail.com> <87txk1txbx.fsf@bzg.ath.cx>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:37845)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rainer.stengele@online.de>) id 1UxDdm-000679-3j
	for emacs-orgmode@gnu.org; Thu, 11 Jul 2013 05:58:23 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <rainer.stengele@online.de>) id 1UxDdl-0008Le-1n
	for emacs-orgmode@gnu.org; Thu, 11 Jul 2013 05:58:22 -0400
In-Reply-To: <87txk1txbx.fsf@bzg.ath.cx>
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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Bastien <bzg@gnu.org>
Cc: Nick Dokos <ndokos@gmail.com>, emacs-orgmode@gnu.org, "noorul@noorul.com >> Noorul Islam Kamal Malmiyoda" <noorul@noorul.com>

Am 11.07.2013 08:38, schrieb Bastien:
> Hi Nick,
> 
> Nick Dokos <ndokos@gmail.com> writes:
> 
>> I just pulled and I get the attached backtrace from org-agenda-list.
>> I tried with -q -l minimal.emacs and it's still there.
>> It's probably caused by commit 42691788273cecb75ec620d40cc5394d2cd95ed1.
>> When I revert that, the agenda comes up properly.
> 
> I'm in a hurry and can't really test right now.
> 
> Can you confirm the following patch fixes it for you?
> 
> Thanks,
> 
> 
> 
> 
Yes, the fix works!