[TxMt] Re: Indented soft wrapping

[Trevor Harmon]

This a good discussion, but getting back to the original question, what is the current “best practice” for an end user wanting to enable intended soft wrap globally?

I remember asking this question years ago, and the response was to create my own personal bundle (e.g., “Trevor’s Bundle”) and add to it a setting like the following:

{	indentedSoftWrap = {
		match = '\A[ \t]*';
		format = '$0\t';
	};
}

I certainly agree this procedure is not very user-friendly, but is it still the way to go? Or have things changed in TextMate 2? Thanks,

Trevor

On Feb 2, 2014, at 7:21 PM, Philippe Huibonhoa <phuibonhoa at gmail.com> wrote:

> That's fair. I was suggesting something in the view menu since that's where most users go to change the soft wrap to begin with and thus seems most discoverable. 
> 
> If I change soft wrap via the view menu and see another soft wrap setting I might be inclined to try it or investigate if things aren't working as expected. 
> 
> Messing with bundles or pref files isn't discoverable or user friendly and should only be reserved for things only power users care about and it sounds like this is bubbling up to he something most users care about. 
> 
> Sent from my iPhone
> 
>> On Feb 2, 2014, at 7:16 PM, Matt Neuburg <matt at tidbits.com> wrote:
>> 
>> 
>>> On Feb 2, 2014, at 6:41 PM, Philippe Huibonhoa <phuibonhoa at gmail.com> wrote:
>>> 
>>> Maybe a setting in the view menu by (the normal soft wrap menu item) that when turned off makes textmate ignore all bundle wrapping settings?
>> 
>> There are two problems I'm having:
>> 
>> * A setting that causes a phenomenon I'm seeing could come from many different places (including a theme or a setting, as well as a language grammar) in a bundle different from the one I think I'm in.
>> 
>> * And then to confuse matters *still more* there are all these global settings, plus the .tm_properties files.
>> 
>> If we did what Philippe suggests, it would be *even more* confusing than it is already: "I'm saying to wrap so why aren't we wrapping?" One more undiscoverable thing off in one more undiscoverable location (the view menu or whatever).
>> 
>> It makes me want to argue for exactly the opposite of what Philippe is saying: there should be NO global settings, NO view menu settings. Everything should be in files that I can actually find, in order to govern and understand what's going on.
>> 
>> But at the same time there needs to be a way, as I suggested earlier, to ask TM2 to *tell* me what's going on - for any given phenomenon, *what* file is causing this behavior / phenomenon, including how it overshadows any other files that are trying to influence the same behavior.
>> 
>> It seems to me that this can't really be that hard to do, because TM2 must *have* a knowledge of this. It has a logic that *causes* any given aspect of what I'm experiencing. So it should surely be able to *tell* me that logic.
>> 
>> m.
>> 
>> --
>> matt neuburg, phd = matt at 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 at lists.macromates.com
>> http://lists.macromates.com/listinfo/textmate
> 
> _______________________________________________
> textmate mailing list
> textmate at lists.macromates.com
> http://lists.macromates.com/listinfo/textmate