From: Hadron <[EMAIL PROTECTED]>
Subject: [Planner-el-discuss] When is a muse file a planner file?
Date: Fri, 26 Jan 2007 12:28:39 +1300
>
> This could be down to documentation.
>
> A muse file (extension .muse) created from within emacs should possibly
> not be populated with the default task/diary/schedule/notes template
> UNLESS the file is in a project muse-project-alist directory.
>
> Opinions?
>
Maybe I'm misunderstanding your point, but that is the behavior I get 'out of
the box'. If I create a file with the .muse extension in the ~/Plans directory,
it will have the template inserted in it. However, if I create the file in some
other directory, it will just be a blank buffer with muse as the major mode.
I use muse all the time for making notes and creating/maintaining web pages,
pdf files, blogs etc. When I open a file with the extension .muse, it is in
muse mode and initially, the buffer is blank.
the template functionality you refer to only happens if I create a .muse file
within my planner directory (i.e. ~/Plans). Muse files created outside of this
directory don't get the template. The planner template functionality is an
extension aded by planner mode and not really something muse knows anything
about.
I think it is important to keep the two concepts/objectives of muse and planner
distinct in your mind. Muse is a powerful wiki style authoring and publishing
tool which you can quite easily customize to your own requirements (even
creating new publishing styles). Planner is a mode which sits on top of muse
and provides specific extensions that support you in managing and organising
your projects, tasks and other information.
What I tend to do is use basic muse mode to write up more formal documentation
associated with a specific project. I normally have this in a project specific
directory and define an entry in the project alist that says what publishing
styles to use for this documentation and where to put it. When I've written a
document, I'll use remember to link that document to a planner project page.
I'll also do this with anything else relating to that particular project -
source code, e-mails, web sites etc. This way, I have the planner project page,
which is a summary of all the information relating to this project. It has the
standard planner project page template with tasks, notes and a report section
showing a breakdown of time spent on particular aspects of the project. Within
this page, there will be links to lots of other documents (source code,
documentation, e-mails etc). Often, these links will all be pointing to places
within a distinct directory tree where I work on aspects of that project. For
example, I have the following setup
~/ -----+- /Plans -- 2007.01.01.muse
| |- 2007.01.02.muse
| |- 2007.01.03.muse
| |- ...
| |- TaskPool.muse
| |- Project1.muse
| |- Project2.muse
|- /Mail
|- /News
|- /Projects -- /Project1 -- /Doc -- ProjectDescription.muse
| | | |- ProjectPlan.muse
| | | |- .....
| | |- /Code -- Makefile
| | | |- HellowWorld.rb
| | | |- /Tests -- testCode1.rb
| | |- /......
| |- /Project2 -- /Doc -- ...
| | |- /Code -- ...
| |- ......
|- /public_html -- Project1 -- ....
| |- Project2 -- ....
|- /tmp
Here, you will find links from the ~/Plans/Project1.muse file to files in the
~/Projects/Project1 subdirectories. There will be a definition in the
muse-project-alist for project 1 that specifies the directory for the project
(i.e. ~/Projects/Project1/Doc), the publishing style (i.e. html), the
publishing directory (~/public_html/Project1) and the document root filename
(i.e. index.html). Any notes, thoughts or ideas I have relating to the project
are put into the ~/Plans/Project1.muse file (usually by using remember). The
actual documentation or write up of the project goes into files within
~/Projects/Project1/Doc). The planner day pages provide a daily breakdown of
things, like meetings and tasks to be performed/started on that day or tracking
time spent on each project.
for me, the key to all this is to *not* think of planner mode as a project
documentation mode, but instead think of it as a project information
organisation mode. The actual documentation of the project is done using muse
mode - planner just helps organise and track or the bits of information which
tend to come in that relate to the project. It provides convenience functions
to help ensure you don't lose bits of information and to help you plan your
activity and monitor how long you are spending on various projects and project
parts. Essentially, it is about organisation and management of information
rather than creation of documents etc. This is a somewhat mirky distinction and
difficult to express adequately. You may find it useful to look at planner mode
from a different perspective - rather than trying to see how you can
modify/customize planner mode to fit your purposes, see how you can re-organise
how you work to get the most out of planner mode. then, after a few months,
start looking at how planner mode can be customized to fit your purposes. I
only suggest this as it seems from many of yor posts that you are trying to
fight the system and make it do what you want. While this is something that
emacs does well, I think you need to really understand what a package has to
offer and its underlying philosophy before you charge in and try to change it
to fit with your world. This has the advantage that often, you will learn new
ways of doing things which you actually find better that may not have occured
to you otherwise.
HTH
Tim
_______________________________________________
Planner-el-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/planner-el-discuss
