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

Re: [PATCH] Simple update to bash completions to prevent unbound variable errors.

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 13, 2009, 05:37 UTC
Message-ID
<7vr637epha.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<496C18D8.9070707@tedpavlic.com>
Ted Pavlic <ted@tedpavlic.com> writes:
Show 5 quoted lines
>>> +# __gitcomp_1 requires 2 arguments
>>
>> ... and $1 and $2 mean?
>
> No clue. Patches are welcome.

To be absolutely honest, I think people with "set -u" in their interactive environment are sick. Bourne shells have been substituting unset variables to empty string for eons, and this is not _my_ itch to scratch.

It seems to be yours, though, and I was merely trying to help.
Previous: Ted Pavlic
Message 9 of 9 in “Simple update to bash completions to prevent unbound variable errors.”
  1. Simple update to bash completions to prevent unbound variable errors.Ted Pavlic, Jan 13, 2009
  2. Junio C HamanoJan 13, 2009
  3. Boyd Stephen Smith Jr.Jan 13, 2009
  4. Ted PavlicJan 13, 2009
  5. Ted PavlicJan 13, 2009
  6. Teemu LikonenJan 13, 2009
  7. Junio C HamanoJan 13, 2009
  8. Ted PavlicJan 13, 2009
  9. Junio C HamanoJan 13, 2009

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.