[SVN] Javascript Punctuation Scopes

Chris Thomas chris at cjack.com
Thu Aug 24 02:19:20 UTC 2006


On Aug 23, 2006, at 10:52 AM, thomas Aylott wrote:

> On Aug 23, 2006, at 1:14 AM, Allan Odgaard wrote:
>> On 23/8/2006, at 7:02, Chris Thomas wrote:
>>
>>> [...] Note that the current top level string.* hierarchy should  
>>> probably be placed under the proposed datatype hierarchy:
>>>
>>> 	inline-data.string.(double-quoted|whatever)
>>
>> One slight inconvenience is that we may want to style data  
>> structures with a faint change in background color, and that  
>> should apply to all but strings -- where strings would have a  
>> changed foreground color.
>>
>> So if we group them, we will see scope selectors like: ‘data -  
>> data.string’. Though as string coloring is the dominant case, and  
>> can still use a simple scope selector, this might not be a real  
>> concern.
>
> I'm all for using scopes to describe the languages as they are.
> But i'm not feeling this data.string business.
>
> String feels like it should be a root element.
> Logically it might make a lot of sense to move it in under  
> something more broad.
> But i can't conceive of an actual use for it.

I'm not without sympathy for that view. But, holistically, I think  
this simple consistency is worthwhile.  I think if you reuse or refer  
to sections of the scope hierarchy for defining other bits of the  
scope hierarchy, you want them to be consistent to make it easier to  
figure out what should be in them.

In any case, I can't give you a usage scenario where I think it  
presently affects the end user all that much either way, and I don't  
feel all that strongly about it, and we can always do a global rename  
later if it turns out we need it.

Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macromates.com/textmate-dev/attachments/20060823/97c4f14c/attachment.html>


More information about the textmate-dev mailing list