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

Re: [Patch] trap: exit: invalid signal specification

From
MLMatthias Lederhofer <matled@gmx.net>
Date
Jun 24, 2006, 16:57 UTC
Message-ID
<E1FuBS1-0006RF-O8@moooo.ath.cx>
In-Reply-To
<200606241555.03147.caglar@pardus.org.tr>
Show 5 quoted lines
> As an example bash (v. 3.1.17) permits lowercase signal names but it converts 
> this lowercase signal names into uppercase ones while interpreting the 
> script. But for our "Turkish has 4 letter "I"s" problem this convert to 
> uppercase one process fails but for bash invalid signal names not be 
> considered a syntax error and do not cause the shell to abort. 

It is ``trap <action> <signal>'' so for the signal part this may be right that this is made uppercase. But action is not modified I guess. So it should be exit because there is no built-in named EXIT in bash:

$ type exit exit is a shell builtin $ type EXIT bash: type: EXIT: not found

So for me it does not seem to work:

$ trap 'err=$?; echo trap; EXIT $?' 0 $ exit 5 exit trap bash: EXIT: command not found [1] 12906 exit 5 bash

Previous: S.Çağlar OnurNext: S.Çağlar Onur
Message 4 of 5 in “trap: exit: invalid signal specification”
  1. trap: exit: invalid signal specificationS.Çağlar Onur, Jun 24, 2006
  2. Junio C HamanoJun 24, 2006
  3. S.Çağlar OnurJun 24, 2006
  4. Matthias LederhoferJun 24, 2006
  5. S.Çağlar OnurJun 25, 2006

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.