Brent Goodrick <bgoodr@xxxxxxxxx> writes: > - Bare minimum: Add a new --no-cr option (e.g., "git --no-cr > ... > - Nice-to-have: Add a "git --no-progress" message that would never > ... > Both options are intended to be independent of each other. I do not think so. --no-progress should imply --no-cr ;-) I do not think it makes much sense to pollute your non-terminal with 100 lines of 1%,2%,3%,...100% if it cannot sensibly do carriage-returns. It may be another knob to tweak, but it's a kind of thing you implement because you could, not because it makes sense. I would be mildly against no-cr. I suspect we may even be able to solve it without adding --no-progress. Perhaps some commands do not have --quiet to squelch progress and teaching them --quiet will solve the issue for you? -- 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
