Hi again, Two quick corrections. Jonathan Nieder wrote: > So if "git gui" were to gain a > documentation viewer widget instead of relying on git web--browse, it > would need the HTML path. Actually, it already uses the HTML path. :) > So while I can't see the harm in exposing --info-path and --man-path, > the current patch seems to do an incomplete job of documenting them. > Perhaps this is about finding the documentation corresponding to a > particular copy of git when a machine has multiple copies? It seems Jon's and my mails crossed. Here's another use case for --man-path: if your frontend wants to fall back to HTML documentation without spawning a man pager when the manpages are not installed, it needs to know where to look. (See also gitgui-0.6.0~32, git-gui: Offer quick access to the HTML formatted documentation, 2007-01-28) -- 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