On 08/25/2011 03:40 PM, Jeff King wrote: > We already provide sane hunk-header patterns for specific > languages. However, the user has to manually map common > extensions to use them. It's not that hard to do, but it's > an extra step that the user might not even know is an > option. Let's be nice and do it automatically. > > Signed-off-by: Jeff King <peff@xxxxxxxx> > --- > I tried to think of negative side effects. That's what I worried about when I last touched this code. Now I'm thinking "what took us so long to do this!!??". > Also, any other extensions that would go into such a list? *.bib diff=bibtex *.tex diff=tex *.[Ff] diff=fortran *.[Ff][0-9][0-9] diff=fortran GNU fortran currently recognizes .fXX where XX is 90, 95, 03 and 08 and probably enables/disables features based on the respective standard. [0-9][0-9] would future proof against fortran f13 and f25 as long as there aren't other extensions that would conflict. Wikipedia says that .for is an extension for fortran, but I've never seen that in the wild. Maybe it's a windows thing (3-char ext). -Brandon -- 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