mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Geralt <usr.gentoo@googlemail.com>
To: Valdis.Kletnieks@vt.edu,
	"Américo Wang" <xiyou.wangcong@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Shebang - why are parameters not splitted on whitespace?
Date: Sat, 6 Dec 2008 13:02:14 +0100	[thread overview]
Message-ID: <fbdd0e50812060402q6aaaed6q6bb345c50ed68b07@mail.gmail.com> (raw)
In-Reply-To: <10860.1228542083@turing-police.cc.vt.edu>

On Sat, Dec 6, 2008 at 6:41 AM,  <Valdis.Kletnieks@vt.edu> wrote:
> On Sat, 06 Dec 2008 01:04:52 GMT, Américo Wang said:
>> On Wed, Dec 3, 2008 at 5:29 PM, Geralt <usr.gentoo@googlemail.com> wrote:
>> > Hello,
>> >
>> > I should have anticipated this objection :-). I'm aware that this is
>> > not consistent among Unix operating systems (you can find more about
>> > it here [1]), but I was specifically refering to linux in this case
>> > and why it handles the shebang arguments as one big string and not as
>> > single arguments for the application.
>>
>> I can't think out any strong reasons, maybe only becasue Linux developers
>> prefer that approach.
>
> And of course, "whitespace" is a somewhat fungible concept.  'man bash'
> and read about $IFS.
>
So you're saying that you can't do that because you don't know where
to split the parameters, right? But would it be that bad to state a
rule what "whitespace" is in the shebang line?

  reply	other threads:[~2008-12-06 12:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-03 15:14 Geralt
2008-12-03 15:56 ` Américo Wang
     [not found]   ` <fbdd0e50812030929q65d2e805y49094dd67209be7e@mail.gmail.com>
2008-12-03 17:29     ` Geralt
2008-12-06  1:04       ` Américo Wang
2008-12-06  5:41         ` Valdis.Kletnieks
2008-12-06 12:02           ` Geralt [this message]
2008-12-06 21:14             ` Aaron Cohen

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=fbdd0e50812060402q6aaaed6q6bb345c50ed68b07@mail.gmail.com \
    --to=usr.gentoo@googlemail.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xiyou.wangcong@gmail.com \
    /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

all inboxes | Powered by JetHome®