From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Annotate files in org syntax Date: Tue, 15 Jan 2008 17:18:08 +0100 Message-ID: <900613C3-47D8-4367-8FFF-B9AE4DC06E5A@gmail.com> References: <87abnb6p0p.fsf@shellarchive.co.uk> <002476B0-3F2A-41B3-BE39-7C1EB9F02AB3@gmail.com> <87odbn47jr.fsf@shellarchive.co.uk> Mime-Version: 1.0 (Apple Message framework v915) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JEpMu-0004H9-DJ for emacs-orgmode@gnu.org; Tue, 15 Jan 2008 12:14:32 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JEpMs-0004Cw-C6 for emacs-orgmode@gnu.org; Tue, 15 Jan 2008 12:14:31 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JEpMr-0004Ca-Uz for emacs-orgmode@gnu.org; Tue, 15 Jan 2008 12:14:29 -0500 Received: from fg-out-1718.google.com ([72.14.220.156]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JEpMr-000666-IC for emacs-orgmode@gnu.org; Tue, 15 Jan 2008 12:14:29 -0500 Received: by fg-out-1718.google.com with SMTP id d23so3662673fga.30 for ; Tue, 15 Jan 2008 09:14:28 -0800 (PST) In-Reply-To: <87odbn47jr.fsf@shellarchive.co.uk> 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: Phil Jackson Cc: org-mode list On Jan 15, 2008, at 1:06 PM, Phil Jackson wrote: > Carsten Dominik writes: > >> Can you say more on how you typically use this? > > At the moment I use it solely with code. Rather than put TODOs in the > code itself I like to keep an org style list. As an off the top of my > head example an entry might look like this: > > * ~/blah.pl > ** TODO [/] Refactor extract_something function :SPAM_ENGINE: > - [ ] 100% unit test coverage > - [ ] Replace substr/index calls with regexps > > As all of these are in one file I can use sparse trees to drill down > to > a project (for example). Thanks. > > > I'm going to hack on it and make it project/branch aware... just > haven't > figured out how yet :) Yes, I guess you might want to have sections corresponding to functions in a source code file or so. Maybe you can get some inspiration from the code i Emacs that produced ChangeLog entires (e.g. `add-change-log- entry'). These commands create an etnry consisting of a file name and some kind of local section like a function name, a section in a texinfo document etc. Best wishes - Carsten