From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: cygwin-bash compat/regression bug... startup line prob
Date: Fri, 02 May 2014 01:33:00 -0000 [thread overview]
Message-ID: <5362F5D9.1010800@redhat.com> (raw)
In-Reply-To: <5362C6A0.3040306@tlinx.org>
[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]
On 05/01/2014 04:11 PM, Linda Walsh wrote:
> The reason the above fails... (I got it to work).. is that if there is a
> space
> on the line after the "-u", that also fails.
>
> I didn't deliberately put one there, but that it no longer handles
> separate options is an evolution of software devolution.
It NEVER worked to put more than one option. I don't know why you are
arguing "software devolution" when there has been no regression in
behavior, rather you are just experiencing something that has always
been this way. And I already explained in the other message that yes
indeed cygwin is different than Linux in that trailing whitespace is
passed through on cygwin but stripped in Linux.
>
> But NOTE -- the above error claims it is coming from /usr/bin/bash.
> That's not my login shell nor on the shebang line.
>
> That's cygwin-black-magic... converting all /bin paths to /usr/bin...even
> shells?...
I already explained in the other mail that this is a side-effect of
cygwin converting to windows paths and then back during execve shebang
computation, rather than preserving the argv[0] of the user. You are
welcome to provide a patch.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2014-05-02 1:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 22:11 Linda Walsh
2014-05-02 1:33 ` Eric Blake [this message]
2014-05-03 19:01 ` Linda Walsh
-- strict thread matches above, loose matches on Subject: below --
2014-04-28 20:43 Linda Walsh
2014-04-28 21:18 ` Eric Blake
2014-05-01 5:57 ` Linda Walsh
2014-05-01 6:41 ` Eric Blake
2014-05-01 18:11 ` Linda Walsh
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=5362F5D9.1010800@redhat.com \
--to=eblake@redhat.com \
--cc=cygwin@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).