From: Intransition Date: 2012-03-11T05:32:51+09:00 Subject: Re: Configuration Convention ------=_Part_3_21812764.1331411568877 Content-Type: multipart/alternative; boundary="----=_Part_4_15215074.1331411568877" ------=_Part_4_15215074.1331411568877 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On Saturday, March 10, 2012 3:30:06 PM UTC-5, Intransition wrote: > > > Something like that, maybe even offer a couple of intelligent variations > (e.g. group the same extensions together or not). While not a true > de-cluttering solution. It would at least help a lot. Maybe if enough of up > put in support requests to Github they would incorporate something like > this. And even easier, maybe someone could write a better `ls`? > s/up/us > These load and high roads are not mutually exclusive. So both are worth > pursuit. > s/load/low/ ------=_Part_4_15215074.1331411568877 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit

On Saturday, March 10, 2012 3:30:06 PM UTC-5, Intransition wrote:

Something like that, maybe even offer a couple of intelligent variations (e.g. group the same extensions together or not). While not a true de-cluttering solution. It would at least help a lot. Maybe if enough of up put in support requests to Github they would incorporate something like this. And even easier, maybe someone could write a better `ls`?

s/up/us 


These load and high roads are not mutually exclusive. So both are worth pursuit.

s/load/low/
 


------=_Part_4_15215074.1331411568877-- ------=_Part_3_21812764.1331411568877--