Junichi Uekawa <[EMAIL PROTECTED]> writes:

>> 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

Oh.  I didn't realize that before.  Since the behavior you want is
already happening at publish time, it is OK to implement it this way
when editing the buffer as well.

> 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)

Thanks for the concise summary.  I've now fixed this upstream, and the
fix will be present in the next release (which ought to happen later
this week).

-- 
       Michael Olson -- FSF Associate Member #652     |
 http://mwolson.org/ -- Jabber: mwolson_at_hcoop.net  |  /` |\ | | |
            Sysadmin -- Hobbies: Lisp, GP2X, HCoop    | |_] | \| |_|
Projects: Emacs, Muse, ERC, EMMS, ErBot, DVC, Planner |

Attachment: pgpRYM1lusaCZ.pgp
Description: PGP signature

Reply via email to