Thread (1 message) 1 message, 1 author, 2016-06-15

Re: [PATCH] Make sure show_all_errors when using porcelain error messages

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:49:27

Matthieu Moy [off-list ref] writes:
Junio C Hamano [off-list ref] writes:
quoted
Matthieu Moy [off-list ref] writes:
quoted
opts.show_all_errors controls the number of errors that can be displayed,
and set_porcelain_error_msgs gives the format. But the formatting would
be incorrect if set_porcelain_error_msgs is called without setting
opts.show_all_errors.
That makes it sound like a design bug of set_porcelain_error_msgs(), in
that the caller _cannot_ choose to stop at the first error if it wants to
use friendlier message than the plumbing one.
You're right that the caller cannot stop at the first error and get
friendly message, but I don't think this is a bug.
I am not saying it is a bug.  The description makes it sound like it is a
bug and I was wondering if it can be worded better not to do so.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help