From: Carsten Dominik <carsten.dominik@gmail.com>
To: Phil Jackson <phil@shellarchive.co.uk>
Cc: org-mode list <emacs-orgmode@gnu.org>
Subject: Re: Annotate files in org syntax
Date: Tue, 15 Jan 2008 17:18:08 +0100 [thread overview]
Message-ID: <900613C3-47D8-4367-8FFF-B9AE4DC06E5A@gmail.com> (raw)
In-Reply-To: <87odbn47jr.fsf@shellarchive.co.uk>
On Jan 15, 2008, at 1:06 PM, Phil Jackson wrote:
> Carsten Dominik <carsten.dominik@gmail.com> 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
next prev parent reply other threads:[~2008-01-15 17:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-12 15:29 Annotate files in org syntax Phil Jackson
2008-01-15 11:06 ` Carsten Dominik
2008-01-15 12:06 ` Phil Jackson
2008-01-15 16:18 ` Carsten Dominik [this message]
2008-01-15 17:31 ` Phil Jackson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=900613C3-47D8-4367-8FFF-B9AE4DC06E5A@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=phil@shellarchive.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.