<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 26 May 2016, at 18:44, Anders Bertelrud <<a href="mailto:anders@apple.com" class="">anders@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">On 2016-05-26, at 00.43, Rob Allen <<a href="mailto:rob@akrabat.com" class="">rob@akrabat.com</a>> wrote:<br class=""><div class=""><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""></div><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Looks nice and consistent to me. I like it.</div></div></blockquote><div class=""><br class=""></div><div class="">Great!</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">It seems like `-vv` is not documented though or has it been removed?</div></div></div></blockquote><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class=""></div><div class="">It’s been removed, since:</div><div class=""><br class=""></div><div class="">a) it is non-standard, and</div><div class="">b) it can be easily achieved using -v -v</div><div class=""><br class=""></div><div class="">I didn’t change the behavior that each occurrence of -v increments the verbosity level.</div></div></div></div></div></div></blockquote><div><br class=""></div><div>Works for me.</div><div><br class=""></div><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Also, it seems slightly strange that there's not a long-form name for test's `-s` option.</div></div></div></blockquote><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class=""></div><div class="">That’s a good point. “specifier” would be the obvious suggestion for a long-form name. Does that sound good to you?</div></div></div></div></div></div></blockquote><div><br class=""></div><div>Personally, I'm not a fan of the word "specifier to mean a single test class/method, and would have picked --case/-c or --test/-t given the choice. </div><div><br class=""></div><div>However, given that the recently chosen short form is -s and the title of that section is "SPECIFIER", then --specifier is nicely consistent.</div><div><br class=""></div><div>Regards,</div><div><br class=""></div><div>Rob...</div><div><br class=""></div></div><br class=""></body></html>