[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[emacs-wiki-discuss] Questions about sectionalize and tags markup
From: |
Andrew J. Korty |
Subject: |
[emacs-wiki-discuss] Questions about sectionalize and tags markup |
Date: |
Thu, 24 Nov 2005 09:32:14 -0500 |
User-agent: |
Gnus/5.110003 (No Gnus v0.3) Emacs/21 (darwin) |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
While porting planner-authz.el to muse (sorry I didn't mention sooner
I was working on it, Michael :-), I was hoping to take advantage of
the sectionalize code, but I ran into a couple of problems.
First, sectionalize seems to run too early -- before any of the markup
or tag rules. So if you have something that looks like, say, a
section heading in the middle of an <example> section, it will get
marked up incorrectly. It happens a lot with snippets from ERC, which
I'll often wrap in <example> tags. By default, ERC begins action
lines with *s, so they look like section headings.
Can anyone think why sectionalize shouldn't be run from a regexp rule?
That way, we could mark text wrapped in <example> tags as read-only
(probably a good idea, if we don't already) so it won't get matched.
Second, muse-publish-markup-tag doesn't seem to understand nested tags
of the same name, which sectionalize produces a lot of. I can think
of two ways around this. Preferably, we'd make
muse-publish-markup-tag able to grok nested tags. Or as a quick fix,
we could have sectionalize name each tag differently (<section1>,
<section2>, etc.).
- --
Andrew J. Korty, Chief Security Engineer, GCIA, GCFA
Office of the Vice President for Information Technology
Indiana University
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (Darwin)
iD8DBQFDhc7y8gM8+Mr5peERAoPQAKDiVy75j7+1lSk1l8W13QNr2OQEPACeJPie
2IW60cwY+dbWTyAZZ+gwuFI=
=KM1I
-----END PGP SIGNATURE-----
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [emacs-wiki-discuss] Questions about sectionalize and tags markup,
Andrew J. Korty <=