On Fri, Jan 15, 2010 at 05:11:07PM +0100, Nicolas Sebrecht wrote: > > I don't understand what you mean. How does "sed" do its own globbing of > > the command line? > > Well, we are in the same dilemma as the other tools. The internal > globbing rules are explained in the related man page. Maybe I wasn't clear: to my knowledge, "sed" does not do any globbing itself. How is this the same situation? Of course other commands like sed will be fed the expansion of a shell glob, and there may be times when you want to feed a subset of an expansion. But that is not my complaint; my complaint was mainly that git's solution to this is not easily discoverable by an uninformed user. Most other commands don't even have a solution (you would have to solve it in the shell to pass the desired expansion to the program). > > when I look in the manual, I am more likely to look for a command-line > > option that helps me rather than to read all of the text > > True. All I can see is to improve the man page with a dedicated section > "Globbing" instead of loosing it in a "random" place. I don't think that would help. The problem is that the user knows they have an issue with ignored files. The solution is custom globbing, but they don't know that. So making globbing more prominent doesn't help, since they will be looking for ignores. You would need to have an "ignore" section that mentions globbing. To be clear: I do not have an actual solution, and my initial message was mostly just grumbling. We _do_ mention globbing and ignores in the same paragraph, as I quoted earlier. So that is probably enough for a diligent user to come up with the solution, or at least enough that trying to improve on it will have diminishing returns. You could even argue that I was not being such a diligent user in my initial response. :) -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