From mboxrd@z Thu Jan 1 00:00:00 1970 From: James TD Smith Subject: Re: Org-mode version 6.32trans (release_6.32b.127.g471c2); Tasks with blank effort show up as 0:00 Date: Tue, 10 Nov 2009 03:06:33 +0000 Message-ID: <20091110030633.GD1426@yog-sothoth.mohorovi.cc> References: <200911091552.nA9FqtQZ025225@gollum.intra.norang.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N7h4A-0001QI-PI for emacs-orgmode@gnu.org; Mon, 09 Nov 2009 22:06:47 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N7h45-0001MO-Q9 for emacs-orgmode@gnu.org; Mon, 09 Nov 2009 22:06:46 -0500 Received: from [199.232.76.173] (port=36194 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N7h45-0001M7-LN for emacs-orgmode@gnu.org; Mon, 09 Nov 2009 22:06:41 -0500 Received: from 81-86-40-42.dsl.pipex.com ([81.86.40.42]:64522 helo=yog-sothoth.mohorovi.cc) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1N7h45-0000Bs-0q for emacs-orgmode@gnu.org; Mon, 09 Nov 2009 22:06:41 -0500 Content-Disposition: inline In-Reply-To: <200911091552.nA9FqtQZ025225@gollum.intra.norang.ca> 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: Bernt Hansen Cc: emacs-orgmode@gnu.org Hi Bernt, On 2009-11-09 10:52:55(-0500), Bernt Hansen wrote: > As part of my weekly review I look for NEXT tasks with no effort > defined. A recent change to org-mode now displays entries with no > Effort property as 0:00 in column view -- these used to be blank. > This is less convenient for me since it's easy to miss tasks with no > effort defined when they don't stand out in the list. > > It's really easy to scan the list of NEXT tasks in column view and see > where there is a blank entry for estimate. It's not so obvious when > the effort value is 0:00 and it's buried in the middle of other tasks > with effort values. Scanning for blank effort NEXT tasks used to take > about 10 seconds but now I have to carefully scrutinize the list to > make sure I didn't miss any. Can you try applying d8865d62646977a2fb15917d63eee680e3ad12e3 in the bugfixes branch at yog-sothoth.mohorovi.cc? That should fix it. James -- |---|