>>>>> "Michael" == Michael Olson <[EMAIL PROTECTED]> writes:
Michael> Phillip Lord <[EMAIL PROTECTED]> writes: >> It uses `match-string' so the groupings in the regexp would have >> to be the same in the new regexp as the last. I suspect you would >> find a few other places in the code where the syntax is hard >> coded -- not to be rude to Michael of course. He may have got rid >> of all these occurrences. Michael> Let me know if you do find occurrences where syntax is Michael> hard-coded, and I'll try to fix them. The biggest one is that you use match data a lot -- you can change the regexp's but they have to have the same groups in the same order. The reason I noticed this, is that I wanted to add support for all markup strings to also be available as tags -- I'd love an anchor tag, for instance, for use in tables and lists. In practice it's hard to do this, as the existing "insert an anchor code" will not be usable if it uses match data. Flip side, taking match-data out is going to be a pain. For others, uses I don't know. I've just noticed when I have written code extending muse, that the syntax (like the meaning of "#" in a link) has had a tendency to creep in. As I say, you're a better coder, so may have avoided it. Michael> I haven't gotten around to implementing support for Michael> pluggable syntaxes. When I do, it will probably take the Michael> form of a :markup-regexps attribute in the directories area Michael> of a muse-project-alist entry. Sounds reasonable to me. Phil _______________________________________________ Muse-el-discuss mailing list [email protected] https://mail.gna.org/listinfo/muse-el-discuss
