On Apr 12, 6:44 pm, Tobias Beer <[email protected]> wrote:
> The current discussion might be a bit misleading in that I started by using
> the term "prefix" and now you are talking about suffixes too.
hihi,
one finger is not enough, we'll take the hand.
> Thus, I would currently vote to change the meta characters like so:
>
> ^PrependToFormattersArray
> -> instead of the ugly "prefix" 0!
Do you have a special usecase, where it is necessary to put a user
defined formatter in front of the core formatters. I personally think,
this will only cause support requests because of broken core
formatting. Just my opinion.
I do like the other suggestions.
> Keep in mind that - at the moment - the wildcard * is only intended to
> serve for word endings.
that's what I thought.
> It currently is not intended to be used as {wild*card} or {*card} or even
> {*middle*}.
> I might check as to how hard it would be to allow it both at the beginning
> or at the end of a term.
I'd give that low priority.
A fast shot regexp for {wild*card} looks like: [\s](wild.*?card)[\s]
{*card} will be harder to create and imo
{*middle*} is a killer because of missing start and end definitions
(at least at 1am ;)
> Eventually, I don't think that these metacharacters should cover the full
> range of what RegEx has in store, because *no one* will want to use that.
I'd not implement this, until someone can name a really good reason
why s/he needs it :)
-mario
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" 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/tiddlywiki?hl=en.
