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

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

[emacs-wiki-discuss] Re: Questions about sectionalize and tags markup


From: Michael Olson
Subject: [emacs-wiki-discuss] Re: Questions about sectionalize and tags markup
Date: Fri, 20 Jan 2006 19:51:30 -0500
User-agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux)

address@hidden (Andrew J. Korty) writes:

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

Is this still an issue with the 3.40 release?  I remember that Peter
K. Lee tweaked planner-publish a bit just before the release.

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

I think that some of the nested tags were renamed in the
aforementioned changes to work around this.

One issue with recognizing nested tags of the same name is that
example/QuickStart.muse uses constructs like
=<literal><literal></literal>= in order to get the text "<literal>"
printed correctly in monospace.  This would be something we'd have to
take into consideration.

-- 
Michael Olson -- FSF Associate Member #652 -- http://www.mwolson.org/
Interests: manga, Debian, XHTML, wiki, Emacs Lisp
  /` |\ | | | IRC: mwolson on freenode.net: #hcoop, #muse, #PurdueLUG
 |_] | \| |_| Jabber: mwolson_at_hcoop.net

Attachment: pgpWmZdzUUiZY.pgp
Description: PGP signature


reply via email to

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