> On 18 Jul 2017, at 5:59 pm, Mark Waddingham via use-livecode
> <[email protected]> wrote:
>
> I think it is worth having a preference for both highlighting and completion
> - it serves people's individual tastes, and as long as the preference is
> discoverable then it won't add any complexity.
OK, I’ll open a report about those
>
> Ideally highlighting would be context aware - so outside of a string, it
> highlights other brackets outside of strings; but when in a string it
> highlights brackets in strings:
>
> put (1 "a(2" & tVar ")2" )1 after tFoo
>
> (Numbers used to indicate matching pairs)
I think it doesn’t currently do what you are suggesting but in the case above
it does what you want anyway ;-)
>
> I was thinking in terms of syntactically - missing the point of in-string
> highlighting (as HH and Mark Wieder pointed out).
>
> Indeed, the current approach is an approximation to the ideal and adding {
> and } to highlighting wouldn't do any harm; and would serve the use-case of
> JSON and similar generation.
>
> In terms of ' then, for much the same reason that would probably be useful -
> although that might require a bit more work on the highlighting code as it
> isn't a matched pair (@montegoulding?).
Should be the same as quote so not a big issue if it’s helpful.
Cheers
Monte
_______________________________________________
use-livecode mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
