|
|
Subject: Re: When does planner commit? - msg#00118
List: emacs.planner.general
John Sullivan <john@xxxxxxxxxxxxxx> writes:
> Hadron <hadronquark@xxxxxxxxxxxxxx> writes:
>
> [...]
>
> > For this reason the include code is better IMO. If you can edit it, it
> > seems appropriate that it is saved back.
>
> I'll clarify the documentation on this. It's something to get used to
> -- there
Great : when you know about it, its ok, but as a beginner it is
confusing.
> are other planner libraries as well that incorporate information into your
> planner pages, but are not intended to provide editing capabilities. You can
> display commit log note information, for example, but editing the log notes on
> your planner page does not edit the log notes themselves.
It seems inherently wrong to me : the presence of the "insinuate"
functions would hint that dependant/source files are updated in the same
way updating a taskpool updates a day page.
--
Was this page helpful?
Thread at a glance:
Previous Message by Date:
click to view message preview
Re: Muse/Planner - how to change project
John Sullivan <john@xxxxxxxxxxxxxx> writes:
> Hadron <hadronquark@xxxxxxxxxxxxxx> writes:
>
> [...]
>
>> The other projects are totally disjoint and feature a lot of different
>> minor tasks many not even scheduled at all.
>>
>
> If they are not scheduled at all, then can you explain why you need separate
> planner projects? If you don't have a need for multiple different pages for
> the
> same day, each in the context of a different project, then it seems like your
> needs can be handled by just using separate Plan pages within one planner
> project.
I wish to keep them seperate for publishing and location reasons. If I
am doing work for two clients I do not want their plan pages anywhere
near each other.
Really as simple as that.
If multiple projects are not supported then possible having
'planner-project is misleading? However, another post about a function
in plannercontrib seems to address it (he wrote it for "home and work"
planner project seperation).
>
>> No, I would want seperate plan pages providing the logical equivalent of
>> categories to further break down the indicidual projects. Each project
>> would have its master TaskPool for generic tasks and the auto generated
>> day page for tasks which have been scheduled.
>>
>
> I suppose I do something like this:
>
> * TaskPoolEmacs
> * TaskPoolWork
> * TaskPoolHome
>
> within my planner-project.
>
> Note that you can divide your task list up with whitespace and planner will
> respect the white space separationq. It also sounds like you might be
> interested in planner-trunk, which provides methods for grouping tasks.
>
> I don't understand the desire to have multiple day pages for the same day. You
> only have one day every day. It seems to me we should be looking for a
> way to
See above.
> display everything you need to do on that day in a visually appealing manner
> in
> one place/file, not figuring out how we can have 5 different files for the
> same
> day to look at?
Really I prefer the concept of seperate projects. But if it isnt
supported that is ok : at a push the seperate plan pages will suffice
for now.
--
Next Message by Date:
click to view message preview
muse-index-as-string and exclusions
Hi,
Narrowing my muse-project-alist to planner pages, I have:
(setq muse-project-alist
`(("Planner"
("~/Plans"
:default "PlannerHome"
:force-publish ("indexPlanner")
:major-mode planner-mode
:visit-link planner-visit-link)
(:base "sl-plan-xhtml"
:path "~/www/WebPlans"
:exclude "[1-9][0-9][0-9][0-9]\\.[0-9]+\\.[0-9]+"))))
The :exclude entry avoids publishing day pages, and this is exactly what I
wanted. However, I have the following in the indexPlanner page:
<lisp>(muse-index-as-string t t t)</lisp>
which includes all day pages, but of course they link to non-existent
pages in this case. Is there some way to make muse-index-as-string aware
of my :exclude pattern? Thanks in advance.
Cheers,
--
Seb
Previous Message by Thread:
click to view message preview
Re: When does planner commit?
Hadron <hadronquark@xxxxxxxxxxxxxx> writes:
[...]
> For this reason the include code is better IMO. If you can edit it, it
> seems appropriate that it is saved back.
I'll clarify the documentation on this. It's something to get used to -- there
are other planner libraries as well that incorporate information into your
planner pages, but are not intended to provide editing capabilities. You can
display commit log note information, for example, but editing the log notes on
your planner page does not edit the log notes themselves.
--
John Sullivan
Emacs Planner Maintainer
http://www.wjsullivan.net/PlannerMode.html
GPG Key: AE8600B6
Next Message by Thread:
click to view message preview
Question about Diary entries and links
Why when I "planner-diary-add-entry" does the resulting diary entry
contain a link back to the plan page but which is not rendered as a
hyperlink in the Diary section of that plan page?
--
|
|