git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v3 1/2] rm: better error message on failure for multiple files

From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
Jun 10, 2013, 17:42 UTC
Message-ID
<vpqtxl5dfrf.fsf@anie.imag.fr>
In-Reply-To
<7v8v2hkhqc.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
Show 11 quoted lines
>> +{
>> +	if (files_list->nr) {
>> +		struct strbuf err_msg = STRBUF_INIT;
>> +		int i;
>> +		strbuf_addstr(&err_msg, main_msg);
>> +		for (i = 0; i < files_list->nr; i++)
>> +			strbuf_addf(&err_msg,
>> +				    "\n    %s",
>
> Is there an implication of having always 4 spaces here to l10n/i18n
> here?  I am wondering if it should be _("\n    %s").

I'd say this is just formatting and should be the same in every languages, but I'm far from an expert in the domain. Maybe some right-to-left languages would need this.

>         test_expect_success 'rm files with different staged content' '
>                 cat >expect <<\-EOF &&
(that should be -\EOF, not \-EOF I think)
>  (2) by using a dash '-' before the end-of-here-text marker, you can
>      align the body of here text with a leading tab (HT).

This works because the list of files is aligned with spaces, but is seems a bit fragile to me to use this -EOF on a text which uses indentation. Anyway, I'm fine with both.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Previous: Junio C HamanoNext: Junio C Hamano
Message 6 of 7 in “rm: better error message on failure for multiple files”
  1. 1/2 rm: better error message on failure for multiple filesMathieu Lienard--Mayor, Jun 10, 2013
  2. 2/2 rm: introduce advice.rmHints to shorten messagesMathieu Lienard--Mayor, Jun 10, 2013
  3. Junio C HamanoJun 10, 2013
  4. Matthieu MoyJun 10, 2013
  5. Junio C HamanoJun 10, 2013
  6. Matthieu MoyJun 10, 2013
  7. Junio C HamanoJun 10, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.