Hi,

Michael Olson <[EMAIL PROTECTED]> writes:

> Planner has deadline timestamps that automatically update themselves
> whenever you do M-x plan to open up the latest daypage. I can't
> imagine a need for "active" or "scheduled" timestamps, whatever those
> are.

Okay. This is where Planner and Org completely diverge.

Planner store all the information in files, and keeping this information
uptodate is planner's job.

Org let's you open dynamic (temporary) views on your agenda files, and
deciding if some task (deadline or what you want) should be part of the
view is computed at display time. This is why there are active and
inactive timestamps.

> What about tasks that might relate to two different projects?

You can use tags to refer to project, then have several tags for a task.
But it's a bit unusual. 

Ordinarily, people have one category for each project. With this
configuration, putting a task into several project would require to
simply copy the task under those projects, which is not very convenient.

> Additionally, you have to hit extra keystrokes in order to evaluate
> the code. That's bad if you have code that you want to be updated
> constantly (like a report), because then the output is stale unless
> you remember to hit those keystrokes periodically.

No additional keystrokes required:

(add-hook 'org-mode-hook
          (lambda() (add-hook 'before-save-hook 
                              'org-update-all-dblocks t t)))

>     (?\< . "\\textless{}")     ; possibly done for look rather than
>     (?\> . "\\textgreater{}")  ; necessity
>     (?\~ . "\\~{}")  ; not mentioned in org notes, but escaped by org
>     (?\@ . "\\@")    ; not escaped, AFAICT
>
> Characters escaped differently by Muse:
>
>     (?\\ . "\\textbackslash{}")
>     (?\_ . "\\textunderscore{}")

This is actually *very* helpful, thanks very much!

> By "see LaTeX formulas", do you mean "generate a PNG file, and then view
> the PNG file from inside of Emacs"?  If so, Muse does not yet have that,
> but it sounds useful; might have to add it in a subsequent release.

Yes, this is what I meant.  Very neat indeed.

> I don't agree with Planner getting a "no" on embedded LaTeX. If it is
> indeed the case that Org can preview LaTeX regions while editing an
> Org file, it would be best to put that in a separate "preview LaTeX"
> entry.

Ok, I've separated preview/embedded in the tables.

  http://www.cognition.ens.fr/~guerry/emacs-planner-org.html

-- 
Bastien

_______________________________________________
Planner-el-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/planner-el-discuss

Reply via email to