From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Bug in checklists Date: Mon, 7 Apr 2008 17:05:35 +0200 Message-ID: <9D325090-5D16-44D7-B9F6-D0B185456256@science.uva.nl> References: <20080405222044.GA23490@dominik-pc> Mime-Version: 1.0 (Apple Message framework v919.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Jitxs-0003Ih-SL for emacs-orgmode@gnu.org; Mon, 07 Apr 2008 12:13:00 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Jitxr-0003HC-Tp for emacs-orgmode@gnu.org; Mon, 07 Apr 2008 12:13:00 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jitxr-0003H1-OC for emacs-orgmode@gnu.org; Mon, 07 Apr 2008 12:12:59 -0400 Received: from ug-out-1314.google.com ([66.249.92.172]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Jitxr-0006hX-E1 for emacs-orgmode@gnu.org; Mon, 07 Apr 2008 12:12:59 -0400 Received: by ug-out-1314.google.com with SMTP id a2so503944ugf.48 for ; Mon, 07 Apr 2008 09:12:57 -0700 (PDT) In-Reply-To: <20080405222044.GA23490@dominik-pc> 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: dominikho@gmx.net Cc: emacs-orgmode@gnu.org On Apr 6, 2008, at 12:20 AM, Dominik Honnef wrote: > Hi. > Recently I installed org (after i viewed some pretty exciting > screencast about it), but i had a hard time to figure out, why the > checklists and especially the progess indicator ([%] or [/]) didn't > work. Whenever I had one of the indicators and I (un)checked one > of the items, emacs froze till I hit C-g. > > After a while I realized that it needs at least one more line, > may it be empty or not, after the list, to work properly. > > I naturally guess this isn't wanted, so I thought, why not > post it to the mailing list. This has been fixed a few days ago, so if you go and pull the latest git version, it should work fine. Thanks for the report. - Carsten