From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Re: org-toc.el - browsable table of contents for Org Date: Sat, 29 Sep 2007 15:21:27 +0200 Message-ID: <87zlz5y5d4.fsf@bzg.ath.cx> References: <87hclla1lb.fsf@bzg.ath.cx> <200709241731.13418.zslevin@gmail.com> <87r6kny87i.fsf@bzg.ath.cx> <87ve9xxvfy.fsf@bzg.ath.cx> 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 1IbcGG-00080Q-HK for emacs-orgmode@gnu.org; Sat, 29 Sep 2007 09:21:36 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IbcGF-0007yo-D8 for emacs-orgmode@gnu.org; Sat, 29 Sep 2007 09:21:35 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IbcGF-0007yb-9n for emacs-orgmode@gnu.org; Sat, 29 Sep 2007 09:21:35 -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 1IbcGE-00024y-VS for emacs-orgmode@gnu.org; Sat, 29 Sep 2007 09:21:35 -0400 Received: by ug-out-1314.google.com with SMTP id m4so1924092uge for ; Sat, 29 Sep 2007 06:21:34 -0700 (PDT) In-Reply-To: (Renzo Been's message of "Sat, 29 Sep 2007 07:37:23 +0000 (UTC)") 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 Renzo Been writes: >> But I like the idea of having some kind of margin, just as linum.el does >> for line numbers: >> http://stud4.tuwien.ac.at/~e0225855/linum/linum.html > > Yes, I had a look at linum, and it looks like a good mechanism that can be of > use in the TOC. If you could make such a margin, that would be great for the > TOC... > >> What kind of information you would like to be displayed in this margin? >> (Remember there is org-toc-info already, so the margin and the echo-area >> should work in a complementary way.) > > Maybe the margin could display how many sub-headings are below the heading that > shows in the TOC? Or how many lines of text there are folded inside it? Or the > number of TODO's that are below it? Please check latest org-toc.el (0.9a): http://www.cognition.ens.fr/~guerry/u/org-toc.el ,----[ org-toc-margin-default-format ] | The default margin format. This is overriden by any occurrence | of #+TOC_MARGIN: in the base Org buffer. | | %l stands for the heading's line number. | %h stands for the number of headings below this heading. | %t stands for the number of TODO items below this heading. | | For example, a format like "%5l hl:%2h td:%2t | " would show: | | 1456 hl: 2 td: 1 | * A headline here | | - this headline is on line 1456 | - there are 2 headlines below it | - there are 1 TODO item among these 2 headlines | | Attention: using a complex margin format for big Org files could | slow down things considerabily. `---- > Or maybe it's better to keep things simple. And put no extra > information in the margin? The default for the margin is "", since I also think it's better to not display too much information by default. > Just put two or three symbols (ones that do not conflict with org-mode) > there, to make the TOC display distinguishable from the base-buffer. You could > use a symbol from the utf-8 coding table. I've put some examples here: > > http://swangdoodles.googlepages.com/Unicodes-for-org-toc.html I added a new background for the TOC. Please tell me what do you think. > What happens is that the TOC-buffer does open. But it is opened as a full view > buffer, > not as a split screen together with the org-file I will investigate, thanks. > What might also be handy is to limit the size of the TOC-buffer. Right > now, what happens when I'm in a large org-file, and use the TOC, is > that it takes over half the screen... For now I just rely on shrink-window-if-larger-than-buffer, which seems fine to me. But If people think we should force a max size for the TOC, let me know. -- Bastien