From mboxrd@z Thu Jan 1 00:00:00 1970 From: Friedrich Delgado Friedrichs Subject: Re: orgmode git: Org agenda todo list headers broken Date: Fri, 2 Oct 2009 11:04:15 +0200 Message-ID: <20091002090415.GA32214@taupan.ath.cx> References: <0F9000D3-6E0B-4324-A2E4-C212796A033B@gmail.com> Reply-To: friedel@nomaden.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mte9h-0002gP-5m for emacs-orgmode@gnu.org; Fri, 02 Oct 2009 05:10:25 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mte9c-0002dI-79 for emacs-orgmode@gnu.org; Fri, 02 Oct 2009 05:10:24 -0400 Received: from [199.232.76.173] (port=54558 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mte9b-0002dF-Um for emacs-orgmode@gnu.org; Fri, 02 Oct 2009 05:10:20 -0400 Received: from dudelab.org ([212.12.33.202]:1792 helo=mail.dudelab.org) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Mte9b-0000Md-JP for emacs-orgmode@gnu.org; Fri, 02 Oct 2009 05:10:19 -0400 Received: from abrasax.taupan.ath.cx (p5DE8A40D.dip.t-dialin.net [93.232.164.13]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Friedrich Delgado Friedrichs", Issuer "User CA" (verified OK)) by mail.dudelab.org (Postfix) with ESMTP id D3EE2228148 for ; Fri, 2 Oct 2009 11:10:18 +0200 (CEST) Resent-Message-ID: <20091002091016.GB32214@taupan.ath.cx> Resent-To: Emacs-orgmode mailing list Content-Disposition: inline In-Reply-To: <0F9000D3-6E0B-4324-A2E4-C212796A033B@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Carsten Dominik Carsten Dominik schrieb: > Wow, that is pretty interesting. ;-) > How are you setting up your TODO keywords? Separately in each file > with #+TODO, or > what else. Globally. > Maybe you can git bisect to find the offending commit - then the fix > should be easy. ---Zitatende--- Hm, git bisect is fun, I might do that later today or maybe starting next week. --=20 Friedrich Delgado Friedrichs TauPan on Ircnet and Freenode ;)