From: Linda Walsh <cygwin@tlinx.org>
To: cygwin@cygwin.com
Subject: Re: cygwin-bash compat/regression bug... startup line prob
Date: Sat, 03 May 2014 19:01:00 -0000 [thread overview]
Message-ID: <53653CFF.5070902@tlinx.org> (raw)
In-Reply-To: <5362F5D9.1010800@redhat.com>
Eric Blake wrote:
> 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.
---
Like I said -- cygwin-black-magic. Converting paths to windows
and back again... only innermost practitioner's of windows-magic would
create such spells! ;-)
> You are welcome to provide a patch.
----
Aw, shucks, that's awfully nice of you, and if my understanding
of cygwin was such that contributing such a patch wouldn't take more time
learning how to make cygwin than designing and implementing the patch,
I might do such, but it wouldn't be the most efficient use of my time.
As it stands I need to work around cygwin ignoring Windows
mount-points and turning them into symlinks too often and would likely
consider fixing that a higher priority task, though since it's a
reverting an "extra hack" put in to treat windows mount-points
(Junctions) as symlinks, I wouldn't think fixing that would be that
difficult,
Personally, I'd like to see linux running as a subsystem on windows
like the old POSIX sybsystem. That would solve all sorts of compat
problems. ;-) (ya, I know, when pigs fly)...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2014-05-03 19:01 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
2014-05-03 19:01 ` Linda Walsh [this message]
-- 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=53653CFF.5070902@tlinx.org \
--to=cygwin@tlinx.org \
--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).