[TxMt] Re: does .tm_properties actually work?

[Allan Odgaard]

On 14 Dec 2013, at 1:53, Matt Neuburg wrote:

> […] as a test I created this: […]
>
> I figured if I open an asciidoc file I should be able to tell if it's 
> suddenly Georgia 18. I don't actually *want* that setting, I just want 
> to see that .tm_properties is functioning! But it isn't. I've put this 
> file in my home folder, in the project containing folder, all over the 
> place. But nothing is changing. m.

A current limitation is that the settings: theme, fontName, fontSize, 
and showInvisibles can only be set globally (that is, in 
~/.tm_properties and not targeting a path/scope). We do however 
recommend all four things to be set via the UI (not ~/.tm_properties).

Additionally, when you change certain settings via the UI (like tab 
size) they are stored for the current file scope (e.g. text.asciidoc) in 
~/Library/Application Support/TextMate/Global.tmProperties and when 
settings are collected, scoped settings rank higher than more local file 
name settings (or more local less specific scoped settings).

What this means is that in your local settings you should use [ 
text.asciidoc ] instead of [ *.asciidoc ] to ensure that less local 
(learned) settings for the “text.asciidoc” scope are not eclipsing 
your extension-based settings (and it then also works for untitled 
files).

I have been meaning to look into how scoped and globbed settings are 
ranked so that a local extension match would trump a less local scope 
match, since this is what most users expect / are not aware of the 
learned scoped settings.