On Thu, Aug 18, 2011 at 10:23:33PM -0700, Junio C Hamano wrote: > > I think of it this way: > > > > If the user thinks of the alias as just another form of "log", then we > > do the right thing: we use log's pager config by default, and respect > > pager.log. They never set pager.foo, because that is nonsensical in > > their mental model. > > > > If the user thinks of the alias as its own command, then they would > > expect pager.foo to work. And it does what they expect. > > > > But like I said, I don't personally plan on using this. It was just the > > only semantics that really made sense to me,... > > I can see that argument, but once you start paying attention to "*.foo", > you have to keep supporting that forever, and also more importantly, you > need to worry about interactions between "*.foo" vs "*.log". Which one > should win? Should they combine if both are defined? My "looks confusing" > includes that can of worms. It seems obvious to me that the more-specific *.foo form would take precedence over the *.log form, and anything else would be crazy. But that is just my gut feeling. If you are confused or worried, then that is enough for me to say it is not worth pursuing. It's not a feature I really care about; it was more about fixing something that looked obviously wrong while I was in the area. -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html