Hi,
> >>
> >> Hmm, I hadn't considered this use case before. Do you use the <lisp>
> >> tag for #title on every page, or just some of them? Do you expect
> >> the <lisp> tag to be evaluated when publishing, or left verbatim (but
> >> with the angle brackets escaped)?
> >
> > I expect <lisp> tag to be evaluated. I use it so that it is possible
> > to configure the values for the page in one place. '#title' seems to
> > be evaluated last, and thus putting the setq in the #title has never
> > worked. This is why <lisp> to do the setq is on the second line.
> >
> > Try the following for a more lively example:
> > ---
> > #title Meeting number <lisp>number</lisp>:
> > <lisp>year</lisp>-<lisp>month</lisp>-<lisp>day</lisp>
> > <lisp>(progn (setq year 2007 month 12 date 15 number 10) "" )</lisp>
> >
> > This is meeting number <lisp>number</lisp> ....
> > You are expected to turn in your entry form by <lisp>(- date 2)</lisp>
>
> My suggestion is to do something like this:
i.e. do not use variables within #title.
> 1. The #title line isn't long.
> 2. The order of operation when evaluating <lisp> tags is clear.
> 3. You don't have to insert a standard template in each file.
> The content of meetings can be only that which actually changes
> between meetings.
> 4. If you decide you want the meeting boilerplate to look different,
> you only have to change one file rather than many.
> For now, I've addressed the problem upstream by making Muse not
> interpret <lisp> tags in #title lines or comments when coloring the
> buffer. The reason for this is that the alternative -- modifying the
> publishing process to support evaluating <lisp> tags in #title lines --
> would be time-consuming when publishing, because Muse would have to
> examine every directive for <lisp> tags.
>
> What do you think?
I don't quite understand what you are trying to say. Are you trying to
tell me do not use lisp values within #title? The change sounds quite
drastic and provides no win from the end-user POV.
The fix required is:
for publishing (to html):
current behavior of evaluating #title after everything else is acceptable
for the buffer editing (font-lock):
re-evaluate #title after everything else is evaluated.
(this is what's broken in the recent release)
(current workaround, run C-cC-l twice when visiting the buffer)
regards,
junichi
--
[EMAIL PROTECTED],netfort.gr.jp} Debian Project
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
