I've included a copy of planner-eej-tags.el. This probably won't work out of the box for most of you - so tread carefully.
What does it do? It adds a "*Tags " section to project pages where you can place white space separated tag names for projects. Why would you want to do that? If you find it difficult to organize your world hierarchically, you can tag your projects according to priority, or by status, or by "venue" (home vs work etc), or by anything you like. Hooray for tags! So after you tag stuff, then what? Then you can harvest that data by opening up project pages with Tag in the name. Open up TagFoo and you get the projects tagged foo. Open up TagFooBar and you get only the projects that were both foo and bar. This works great for things like TagWorkHigh. Anything else? Why yes! Thanks for asking. It will also presume tags can be found in the project names themselves. So if you a project page done as WorkOnFooBar will get the tags work, on, foo, bar. Useful if you are marginally consistent in your naming scheme. So what did I have planned for this? Well - there is some lingering debris in my implementation that was going to become a building block for a NextActions like GTD pages. I wanted to be able to easily harvest all "next actions" (perhaps labelled as "A" or pending ala 'o') according to tags. So NextActionsHighWork would cull the actions from all the pages that had both the tags high and work and bring out the next actions. I haven't finished that yet. So if its not done, is it kind of broken? You bet. It is very tempermental and has some notable windows/config assumptions in eej/planner-tags-harvest-tags. It only harvests tags at startup time, so we have to cruise all the project files. Furthermore, I assume no hierarchy and to speed up performance, I cripple planner while I harvest the tags. And of course, there's a performance hit while the tags are culled at emacs start up time. Bad programmer! Bad programmer! To utilize this - you'll need to add (require 'planner-eej-tags) and a (eej/planner-tags-auto-insert-tags) to your planner-mode-hook function. Areas that I want to fix next... a) harvest tags as they are created on the fly - just need to find the right hooks. b) Prevent Tag* files from being written out. They are always auto generated c) Current tags harvesting smells evil - and assumes my config, bad bad bad d) Get NextActions to work and not anger planner-multi -Eric
planner-eej-tags.el
Description: Binary data
_______________________________________________ Planner-el-discuss mailing list [email protected] https://mail.gna.org/listinfo/planner-el-discuss
