> why would you have a link without whitespace after

It's not uncommon to place several links immediately adjacent to each
other and use CSS padding (or margins) to control the whitespace in
between them.

For this particular regexp, I don't think it's safe to assume that any
change outside of the URL pattern itself would be even remotely
backward-compatible.  If we restrict ourselves to considering changes
only within the second (.*?) part of the regexp, then it's potential
impact on existing functionality is more controllable.

So, the problem can be more specifically stated:

Can we determine a "non-greedy" expression that could replace this
portion of the overall regexp and would succeed in matching a URL that
contains a non-encoded ]] sequence, while leaving the terminating ]]
at the end of the PrettyLink alone so that the trailing portion of the
regexp can still match as it currently does?

I think that it *might* be possible to get there... but, as I said,
working that deep in regexp gives me nosebleeds.  Also, we should
really acknowledge that this discussion is really somewhat academic:
inasmuch as the usage of the PrettyLink syntax is so integral to
TiddlyWiki, it is unlikely that *any* kind of change to the existing
pattern could reasonably be considered safe *enough* to make it into
the core...

... still, it's an interesting nut to crack and, if you manage to find
a definitive solution *and* offer a persuasive analysis that proves it
to be 100% backward-compatible with existing usage, it may be possible
to affect a change in the core in some future release.

-e
Eric Shulman
TiddlyTools / ELS Design Studios

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" 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/TiddlyWikiDev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to