On Fri, Feb 20, 2009 at 10:09 AM, Hans <[email protected]> wrote: > > 2009/2/20 The Editor <[email protected]>: > >> Originally, the pattern was delimited by field: some text\n\n. So you >> could have multiline snippets. Unfortunately the code now reroutes >> through the info var function, which just goes to the end of the line. >> I'll fix it one way or another in the next release though. > > I think a pattern like text\n\n will not serve well enough. > I think for multi-line snippets it needs some kind of end marker, > perhaps a beginning and an end marker (like a hidden (:name: var:) in > PmWiki), or something like > > $Var = [@ > multi-line > snippet > text > @] > > (using PmWki code markup as example) > > or any other kind of end marker, but not just an empty line, as empty > lines may well be used inside the snippet.
Of course the whole idea is to keep it as simple and intuitive as possible. BoltWire really tries to simplify markups. There are pro's and con's to this, but I personally lean toward the simplicity side. Seems we had a similar discussion about this recently. :) In this case, I think there are probably work arounds in situations when there is a need for \n\n in the snippet. Even a space before one of the line return would be enough. I'm not opposed to a different delimiter, just not convinced we need it. Here are some possibilities. Perhaps: field: var <> field: var var var <> or field: var ---- field: var var var ---- Though of course then you have the problem that you might need an hr in the snippet. John, I just saw your post and thought about that as a possibility also. Perhaps even a combination, like field: var field: var [[#field]] var var [[#end]] That would work nicely, thought the regex pattern could be tricky... Still, I'd just as soon stick with the simpler format until we have a definite need for something more complex. And then again, what I'll probably end up doing is making the snippets pattern configurable, so admin's can choose different syntax if they desire. A simple $BOLTsnippetsPat variable. Just thinking out loud. I'm away from home at the moment and can't actually implement this. We'll see what we can do when I get around to testing the different possibilities... Cheers, Dan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
