> On 17 Jul 2017, at 11:36 pm, Mark Waddingham via use-livecode
> <use-livecode@lists.runrev.com> wrote:
>
> Okay, so having just read the form thread as well...
>
> There are two things here:
>
> 1) Bracket highlighting
>
> 2) Bracket completion
>
> They should both be preferences.
>
> Secondly, both should really only function on 'real' tokens which are part of
> script (hence why '{' isn't appropriate at this time for it to function on).
> If you are typing a string or a comment then it shouldn't trigger completion
> nor highlighting. This is actually quite hard to get right efficiently
> (indeed, a lot of editors don't get this right, so I end up turning such
> features off).
Actually it’s quite helpful within strings. Consider a string to be used with
the merge function or just the likelihood of wanting a pair of brackets in a
string rather than a single one. As for quotes as they are not valid within a
string if you are typing one it’s highly likely you want two and to concatenate
something between. For example:
put “foo baz”
— come along later and edit to
put “foo” && tBar && “baz”
There is already an autocomplete preference which the bracket completion and
control structure completion checks but it’s currently not exposed in the IDE
UI. Do we want fine grained control over which parts of autocompletion we want
active? That could be confusing.
Bracket highlighting does need a color pref… I guess if this is empty it could
turn it off entirely if people want that.
Cheers
Monte
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
