emacs-wiki-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[emacs-wiki-discuss] Re: Blogging, remembering, planning (was Re: changi


From: Andrew J. Korty
Subject: [emacs-wiki-discuss] Re: Blogging, remembering, planning (was Re: changing planner-directory on the fly
Date: Fri, 02 Jul 2004 12:59:04 -0500
User-agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3.50 (gnu/linux)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

TC <address@hidden> writes:

> planner-authz.el makes reference to "Mason" which, until now, I'd never
> heard of. Googling around gets me the basic idea, but how do I tell if I
> have mason already installed?  FWIW, Gary's planner-authz did seem to
> insert some gobbledygook into the html, but it is simply being
> interpreted as plain text; viz:
>
>    This should be visible. But <&: authz.mas:content, 'users',     
>    [qw(wibble)] &>this should not.
>
> I'm assuming that its failure to be handled correctly suggests
> I *don't* have mason installed.  But how do I confirm that?

This is where it gets a bit convoluted to avoid emacs-wiki's table
handling.  The actual Mason should end up looking like

    This should be visible. But <&| authz.mas:content, 'users',
    [qw(wibble)] &>this should not</&>.

The <&: gets changed to <&| to avoid being marked up as a table.  I
know it's inelegant, but I'm open to ideas.

I can't think of any situation where Mason would get installed by
default or without you knowing it, so you probably don't have it.  For
people who aren't interested in Mason, it ought to be pretty easy to
make planner-authz support SSI or PHP.  The only reason it doesn't now
is that I don't use those things.

- -- 
Andrew J. Korty, Principal Security Engineer, GCIA, GCFA
Office of the Vice President for Information Technology
Indiana University
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA5aJo8gM8+Mr5peERAo+iAJ9ePC0XG9X3tTNEDezyyRM1VLk7jQCg7t/4
StP13ldBdMF42opr6nsrZ4E=
=+JLh
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]