On Sat, Feb 16, 2008 at 11:15:41AM -0800, Junio C Hamano wrote: > Because we spawn the pager as the foreground process and feed > its input via pipe from the real command, we cannot affect the > exit status the shell sees from git command when the pager is in > use (I think there is not much gain we can have by working it > around, though). But at least it may make sense to show the > error message to the user sitting in front of the pager, perhaps > like this. > > What do people think? Have I overlooked any downsides? I think this makes sense. It could be annoying if chatty stderr output got mixed in with the actual output, making things harder to read. But git is not very chatty in general, and the point is that things sent to stderr _should_ grab the user's attention. The only downside I see is that it disrupts the parsing of the output. In most cases, this doesn't matter, since anything parsing the output will disable the pager. The notable exception is something like 'tig', which I believe can act as a git pager which understands the output; it can potentially be confused by the extra lines on stdout. -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
