Re: [tlug] TODO extension for source code and Emacs

[Ian Wells <ijw@example.com>]

On 18/01/06, Stephen J. Turnbull <stephen@example.com> wrote:

(b) [the do-yourself-a-favor-don't-do-that answer] I don't understand
your use case.  Eg, when I want a to-do list as a piece of text, M-x
occur ... C-x o C-x h M-w etc etc does the trick.  However, mostly the
occur buffer *is* the to-do list, and I just change TODO to DONE in
place, then pull all my DONEs together with M-x occur and move them
from in situ to NEWS before the release.

Can you be more specific about what you're trying to do?  Is it just
that you don't leave Emacs running for months at a time, and/or
explicitly kill buffers that are potentially related to current work?
Since I do run Emacs for long periods and don't kill buffers, most of
what's interesting is in a buffer where M-x occur can find it.  This
is faster and more targeted than grep -r.

1. Emacs stays open all the time and for long periods although I don't quite see how this relates to what I was saying.  No, I don't keep all my project's files open all at the same time, and yes, I do kill buffers occasionally.
2. I still don't see what occur does that M-x grep doesn't do better.
3. I think I'd like to have comments on progress and scheduling of TODO marked tasks that are in the source without having the additional notes in the source.  Clearly this is going to be a complete arse.  I'm not sure I've got how I would use this straight in my head, though (hence looking for someone else who'd done it already).

M-x occur seems to be not-totally-working in my Emacs (in the sense that C-x o C-c C-c doesn't switch live buffers back to the target - so it does move point in the target buffer but the *Occur* buffer remains active.  ibuffer-occur exists, I note, and is even nicer, and even more broken on my system (C-c C-c gives an error about closed buffers).

Something good has come of today, anyway, because ibuffer is a command I didn't know about (and useful-looking, too).

--
Ian.
--
Ian.