All of lore.kernel.org
 help / color / mirror / Atom feed
From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [Patch] trap: exit: invalid signal specification
Date: Sat, 24 Jun 2006 15:54:55 +0300	[thread overview]
Message-ID: <200606241555.03147.caglar@pardus.org.tr> (raw)
In-Reply-To: <7vejxf5ktc.fsf@assigned-by-dhcp.cox.net>

[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]

Cumartesi 24 Haziran 2006 05:50 tarihinde, Junio C Hamano şunları yazmıştı: 
> I am not quite sure what to make out this...  Do you mean your
> shell does not like the command "exit" spelled in lowercase
> under Turkic locale?

Sorry to not clear enough previously, for Turkic locales (tr_TR, az_AZ etc.) 
upper(i) != I. More detailed analysis can be found at 
http://www.i18nguy.com/unicode/turkish-i18n.html, "Why Applications Fail With 
The Turkish Language" section. This is the main reason of this problem. 

According to its man page signals defined with uppercase letters but also 
different trap implementations may permit lowercase signal names as an 
extension. 

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. 

Yours
-- 
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/

Linux is like living in a teepee. No Windows, no Gates and an Apache in house!

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-06-24 12:55 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 [this message]
2006-06-24 16:57     ` Matthias Lederhofer
     [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=200606241555.03147.caglar@pardus.org.tr \
    --to=caglar@pardus.org.tr \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.