On Thu, Mar 29, 2012 at 10:16 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Jonathan Nieder <jrnieder@xxxxxxxxx> writes: > >> Filling in the blank at compile time would be possible, but I'm not >> convinced it's a good idea. Wouldn't the same user be just as puzzled >> when >> >> http://git.kernel.org/?p=git/git-htmldocs.git;a=blob_plain;f=git-var.html >> >> (or whatever page with a nicer URL arises to replace the old >> www.kernel.org/... pages) says the fallback is 'vi' and git behaves >> differently? > > I've already rejected this patch once, but that was primarily because the > patch was not justified with the above "I read everybody else's git uses > 'vi' on the Interweb, and even though my distro's manual page says it uses > 'nano', I didn't bother to read it." scenario. I like this original patch, and I like being able to refer to "the" online docs wherever I and google may happen to find them. Because "my distro" may be a resource-constrained minimal OS which omitted the git manual. The same system for similar reasons may default to 'nano' & 'more' if vi and less are unavailable. Phil -- 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