From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Tiny bugs (and org-toggle-comments?) Date: Tue, 21 Nov 2006 18:01:29 +0100 Message-ID: <87psbg68eu.fsf@tallis.ilo.ucl.ac.uk> 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 1GmZ04-0001dO-Kr for emacs-orgmode@gnu.org; Tue, 21 Nov 2006 12:01:36 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GmZ00-0001bB-S6 for emacs-orgmode@gnu.org; Tue, 21 Nov 2006 12:01:34 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GmZ00-0001ax-JY for emacs-orgmode@gnu.org; Tue, 21 Nov 2006 12:01:32 -0500 Received: from [213.36.80.91] (helo=mail.libertysurf.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GmYzz-0002vk-UF for emacs-orgmode@gnu.org; Tue, 21 Nov 2006 12:01:32 -0500 Received: from tallis.ilo.ucl.ac.uk (83.157.203.158) by mail.libertysurf.net (7.3.117.3) id 455B2F29001809C4 for emacs-orgmode@gnu.org; Tue, 21 Nov 2006 18:01:10 +0100 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 Hi Carsten, - links are not recognized as links in the agenda buffer - M-TAB expands ":ta" to ":tag:" (which is correct) but M-TAB expands ":tag" to ":tag" (":" lacking) - Comment regions are not filled (auto-fill is just ignored). Maybe that's not a bug, but I think we should be able to turn filling on for comment regions if needed. Since i'm on this, What about org-toggle-comment-at-point that would hide/show comment under the point? org-toggle-comments that would do this on the whole buffer? Not sure about this though. - Time clocking : When clocking in-and-out on a single task several times, it may end up in a long list of "CLOCK: []" lines. We might be only interested in the "how much time" we spent, not the exact "when". In this case, clocking in would open a temporary "CLOCK:" line, but clocking out would just leave a single "TIME:" line as a summary of the time spent. And maybe this "TIME:" line would also be useful for those who want to use the normal CLOCK: system. I think it would be great if we could chose between the two systems. - Other C-c C-c capabilities (?) C-c C-c on time intervals could update the "=> ..:.." result C-c C-c on other time intervals could display the interval (in the minibuffer) Best regards, -- Bastien