all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ciss <pechorin.andrey@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: TODO in code and org mode
Date: Fri, 29 Jan 2010 09:25:57 -0800 (PST)	[thread overview]
Message-ID: <af252acd-ce1b-4945-ae6e-6133106e602a@k19g2000yqc.googlegroups.com> (raw)
In-Reply-To: mailman.1402.1263474366.18930.help-gnu-emacs@gnu.org

On Jan 14, 4:04 pm, andrea <andrea.crott...@gmail.com> wrote:
> I had an idea which would be really nice if I'm able to implement it.
> I write very often in code comments like
> // FIXME: infinite loop
> for example, now is a good thing they're in the code, but I also would
> like to centralize the error management per project in some way.
>
> So I thought something like, adding a hook in after-save-hook that
> checks all the FIXME|TODO... and adds it to an org-mode file.
>
> That org-mode should be like
>
> * FIXME [[file:error.c:20][error.c]] (don't remember the syntax)
>
> Maybe also including the date when this has been written the first time.
> Then if the error is corrected or the nice thing would be adding a
>  CLOSED at [date]
>
> line.
>
> The only problem I see is if you change the text but leave the FIXME,
> in that case maybe the other thing is not CLOSED but it's just changed,
> and we should remove the old and create a new entry.
>
> What do you think, could that be a good idea?
> Thanks

yes! this is very nice.
i will realise this in future for my ruby-code-editing :)
contact me if u want to talk about anythink -
pechorin.andrey@gmail.com (jabber)


       reply	other threads:[~2010-01-29 17:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1402.1263474366.18930.help-gnu-emacs@gnu.org>
2010-01-29 17:25 ` Ciss [this message]
2010-01-14 13:04 TODO in code and org mode andrea

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=af252acd-ce1b-4945-ae6e-6133106e602a@k19g2000yqc.googlegroups.com \
    --to=pechorin.andrey@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /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.