git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Lederhofer <matled@gmx.net>
To: "S.Ça??lar Onur" <caglar@pardus.org.tr>
Cc: git@vger.kernel.org
Subject: Re: [Patch] trap: exit: invalid signal specification
Date: Sat, 24 Jun 2006 18:57:41 +0200	[thread overview]
Message-ID: <E1FuBS1-0006RF-O8@moooo.ath.cx> (raw)
In-Reply-To: <200606241555.03147.caglar@pardus.org.tr>

> 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

  reply	other threads:[~2006-06-24 16:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-24  1:10 [Patch] trap: exit: invalid signal specification S.Çağlar Onur
2006-06-24  2:50 ` Junio C Hamano
2006-06-24 12:54   ` S.Çağlar Onur
2006-06-24 16:57     ` Matthias Lederhofer [this message]
     [not found]     ` <f36b08ee0606241311h399c42b0h11638f14d6f54bd5@mail.gmail.com>
2006-06-25 14:33       ` S.Çağlar Onur

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1FuBS1-0006RF-O8@moooo.ath.cx \
    --to=matled@gmx.net \
    --cc=caglar@pardus.org.tr \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).