From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Column view bugs Date: Sat, 13 Oct 2007 14:50:15 +0100 Message-ID: <874pgvktt4.fsf@bzg.ath.cx> References: <6befca6f021e58dcdaab748fe501edec@science.uva.nl> 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 1IggSP-0005p1-Ng for emacs-orgmode@gnu.org; Sat, 13 Oct 2007 08:51:05 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IggSM-0005mq-4b for emacs-orgmode@gnu.org; Sat, 13 Oct 2007 08:51:05 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IggSL-0005md-NG for emacs-orgmode@gnu.org; Sat, 13 Oct 2007 08:51:01 -0400 Received: from ug-out-1314.google.com ([66.249.92.174]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IggSK-0000pl-Vn for emacs-orgmode@gnu.org; Sat, 13 Oct 2007 08:51:01 -0400 Received: by ug-out-1314.google.com with SMTP id a2so41425ugf for ; Sat, 13 Oct 2007 05:50:59 -0700 (PDT) In-Reply-To: <6befca6f021e58dcdaab748fe501edec@science.uva.nl> (Carsten Dominik's message of "Sat, 13 Oct 2007 11:28:56 +0200") 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: emacs-orgmode@gnu.org Carsten Dominik writes: >> M-f M-b jump around in a confusing way in column view. Maybe just make >> them like C-f and C-b? > > Good idea. > > Question back: TAB does still cycle visibility in column view, > even though this looks like a table and one might expect > that tab moves to the next field. Any thoughts on this? I'm not expecting TAB to jump from field to field here, but maybe others would. A possible trade-off: do the normal cycling when at the beginning of the line, jump among fields otherwise? >> Is having the column view print practical? What about export? > > Yes, clearly important missing features. What should we have? > > One interesting possibility would be a dynamic block that > captures the column view as an Org-mode table. That would definitely be nice! > The problem here is, where to create it. Globally for the entire > buffer with a #+COLUMNS line is probably the best? Yes. While we are at this, what would people think of a new {%} summary type for column view? {%} Progress status, [100%] if all children are in a DONE state. -- Bastien