Am I the only one who can't get .tm_properties files to *do* anything?
For example, as a test I created this:
[ *.asciidoc ] spellChecking = false tabSize = 4 fontName = "Georgia" fontSize = 18 softTabs = true
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.
-- matt neuburg, phd = matt@tidbits.com, http://www.apeth.net/matt/ pantes anthropoi tou eidenai oregontai phusei Programming iOS 7! http://shop.oreilly.com/product/0636920031017.do iOS 7 Fundamentals! http://shop.oreilly.com/product/0636920032465.do RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html TidBITS, Mac news and reviews since 1990, http://www.tidbits.com
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.
Very helpful, thank you! - A significant issue here is that there is no definitive current documentation about this, and the Internet is now filled with false information giving the very clear impression that what I tried should have worked. m.
On Dec 13, 2013, at 8:47 PM, Allan Odgaard mailinglist@textmate.org wrote:
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.
-- matt neuburg, phd = matt@tidbits.com, http://www.apeth.net/matt/ pantes anthropoi tou eidenai oregontai phusei Programming iOS 7! http://shop.oreilly.com/product/0636920031017.do iOS 7 Fundamentals! http://shop.oreilly.com/product/0636920032465.do RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html TidBITS, Mac news and reviews since 1990, http://www.tidbits.com
Looks like a book writing opportunity! I haven¹t seen anything to suggest ³TextMate Power Editing for the Mac² by James Edward Gray II will be updated.
Dave.
On 16/12/2013 19:38, "Matt Neuburg" matt@tidbits.com wrote:
Very helpful, thank you! - A significant issue here is that there is no definitive current documentation about this, and the Internet is now filled with false information giving the very clear impression that what I tried should have worked. m.
On Dec 13, 2013, at 8:47 PM, Allan Odgaard mailinglist@textmate.org wrote:
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.
-- matt neuburg, phd = matt@tidbits.com, http://www.apeth.net/matt/ pantes anthropoi tou eidenai oregontai phusei Programming iOS 7! http://shop.oreilly.com/product/0636920031017.do iOS 7 Fundamentals! http://shop.oreilly.com/product/0636920032465.do RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html TidBITS, Mac news and reviews since 1990, http://www.tidbits.com
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
--------------------------------------------------------------------- Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
On 17 Dec 2013, at 2:38, Matt Neuburg wrote:
Very helpful, thank you! - A significant issue here is that there is no definitive current documentation about this, and the Internet is now filled with false information giving the very clear impression that what I tried should have worked.
FYI next build will have glob settings rank higher than the (implicitly learned) scoped settings: https://github.com/textmate/textmate/commit/45db36234c82cb97d765e8e3dbb382ce...
And as I’ve said a few times before, the incomplete manual is a large part of why I keep the alpha label on 2.0.