I've just noticed that foldings are not working with the Tcl language. In the following program:
proc foo {args} \ { switch -exact -- $var { match {
} default {} }
}
I don't get any foldings even though they Tcl syntax defines them like so:
foldingStartMarker = '{\s*\?$}'; foldingStopMarker = '^\s*}';
Any ideas?
Thanks,
-Oscar
P.S. Can we add '_', '.', ':', and [0-9] to the list of valid variable characters?
{ name = 'variable.other.tcl'; comment = 'FIXME what are legal variable characters? --Allan'; match = '$([a-zA-Z_.:][a-zA-Z_0-9.:]+(([^)]+ ))?|{[a-zA-Z ]*})'; }
-- pgp fingerprint: BC64 2E7A CAEF 39E1 9544 80CA F7D5 784D FB46 16C1
On 26/10/2005, at 6.58, Oscar Bonilla wrote:
I've just noticed that foldings are not working with the Tcl language. In the following program: [...]
I don't get any foldings even though they Tcl syntax defines them like so:
foldingStartMarker = '\{\s*\\?$}'; foldingStopMarker = '^\s*\}';Any ideas?
That start marker pattern seems rather broken. I have changed it to: '{\s*$'
P.S. Can we add '_', '.', ':', and [0-9] to the list of valid variable characters?
{ name = 'variable.other.tcl'; comment = 'FIXME what are legal variable characters? --Allan'; match = '$([a-zA-Z_.:][a-zA-Z_0-9.:]+(([^)] +))?|{[a-zA-Z ]*})'; }
Done. This is the rule for variables embedded in strings, should the other variable also include these (that one currently matches '$\w+')?
Btw: '.' has no special meaning inside […], so no need to escape it (same goes for ')').
-
Allan Odgaard -
Oscar Bonilla