From: Samuel Wales <samologist@gmail.com>
To: andrea <andrea.crotti.0@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: From comments in code to org-mode
Date: Fri, 5 Feb 2010 17:07:17 -0700 [thread overview]
Message-ID: <20524da71002051607h1fdf9bd2gb8408ebca9c18693@mail.gmail.com> (raw)
In-Reply-To: <m1ljfxx446.fsf@gmail.com>
Ideally we could put tasks in comments, but there are regexps that
need refactoring.
On 2010-01-16, andrea <andrea.crotti.0@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?
> Is there maybe a way to do it?
>
> PS. sorry for the crossposting but here is more appropriate I guess
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
--
Q: How many CDC "scientists" does it take to change a lightbulb?
A: "You only think it's dark." [CDC has denied ME/"CFS" for 25 years]
==========
Retrovirus: http://www.wpinstitute.org/xmrv/index.html
prev parent reply other threads:[~2010-02-06 0:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-16 19:05 From comments in code to org-mode andrea
2010-02-06 0:07 ` Samuel Wales [this message]
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=20524da71002051607h1fdf9bd2gb8408ebca9c18693@mail.gmail.com \
--to=samologist@gmail.com \
--cc=andrea.crotti.0@gmail.com \
--cc=emacs-orgmode@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.