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

Re: [PATCH] shell-prompt: clean up nested if-then

From
Simon Oosthoek <s.oosthoek@xs4all.nl>
Date
Feb 19, 2013, 08:17 UTC
Message-ID
<5123350D.4010802@xs4all.nl>
In-Reply-To
<7vtxp98bmx.fsf@alter.siamese.dyndns.org>
On 19/02/13 00:07, Junio C Hamano wrote:
Show 7 quoted lines
> 
> I think you are misreading a suggestion that is somewhat misguided
> (yes "[ <condition> && <another> ]" does not make sense, but that is
> not applicable to "test <conditon> && test <another>"); ignore it.
> 
> It is fine to write "test <condition> && test <another>" and that
> works portably to even pre-posix systems.
(that's like doing "ls file && rm file" )
Show 5 quoted lines
> 
> But the existing code the patch touches favors [] over test
> consistently; that alone is a good reason to stick with [] in _this_
> script, even though it is against Git's overall shell script style.
> 

I suppose it would be fine if a patch was sent to update the entire git-prompt.sh code to be more in line with the Git shell script style...

My original gripe was just with doing it in one place while leaving all the others unchanged. It makes for messy reading and leads to confusion.

Cheers
Simon
Previous: Junio C HamanoNext: Junio C Hamano
Message 7 of 8 in “shell-prompt: clean up nested if-then”
  1. shell-prompt: clean up nested if-thenMartin Erik Werner, Feb 18, 2013
  2. Jonathan NiederFeb 18, 2013
  3. Martin Erik WernerFeb 18, 2013
  4. shell-prompt: clean up nested if-thenmartinerikwerner@gmail.com, Feb 18, 2013
  5. Jonathan NiederFeb 18, 2013
  6. Junio C HamanoFeb 18, 2013
  7. Simon OosthoekFeb 19, 2013
  8. Junio C HamanoFeb 19, 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.