Duy Nguyen <pclo...@gmail.com> writes:
> On Tue, Feb 12, 2013 at 6:13 AM, Erik Faye-Lund <kusmab...@gmail.com> wrote:
>> Because our command-line parser considers only one byte at the time
>> for short-options, we incorrectly report only the first byte when
>> multi-byte input was provided. This makes user-erros slightly
>> awkward to diagnose for instance under UTF-8 locale and non-English
>> keyboard layouts.
>> Make the reporting code report the whole argument-string when a
>> non-ASCII short-option is detected.
> Similar cases:
> config.c:git_default_core_config() assumes core.commentchar is ascii.
> We should catch and report non-ascii chars, or simply accept it as a
That one is just an uninterpreted byte. core.commentString might be
a nice extension to the concept, but it is an entirely different
> builtin/update-index.c:cmd_update_index(): error("unknown switch
> '%c'", *ctx.opt);
This one is in the same category as this topic.
> builtin/apply.c:apply_one_fragment(): error(_("invalid start of line:
> '%c'"), first); where 'first' may be a part of utf-8 from a broken
This is where the patch is expected to have either " ", "-" or "+",
again, anything else is an uninterpreted byte. It is more like
reporting the file we found an error in, whose filename is not
encoded in UTF-8 to the user's terminal.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html