This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: pwd option to return windows path

I took the liberty to zap mr. peschko as of now from my inbox as background
noise (using a microsoft product which uses paths 'correctly' aka. ms-dos
style). It can't be considered spam since he does not OFFER anything of
dubious or real value. I believe he would be a valuable asset to microsoft
newsgroups, but his contributions to THIS mailing list consist of endless
threads about opinions without any merit. I waited when he offered to tune
-whatever it was; oh yes mingw/cygwin- to his liking; if he WOULD contribute
more than his valuable opinions. Did not happen! But the mingw/cygwin issue
got reawakened like zombies in a cheap horror flick as of this email. So
instead of telling us how much cygwin sucks I would suggest he stays with
windooze which seems to find his undivided approval. I do not really
comprehend why he is even on this list wasting bandwidth that I need so
dearly to download important illegal mp3's.

Last not least, IF the information exchanged would be of any value to the
community it should be led in public and not as threatened to poor
Christopher again in privacy. Since this discussion -again- is of no real
value to anybody I suggest that he sends private emails (and public ones)
from now on to /dev/null/ so that my microsoft filtering product @
e:\program files\microsoft office\outlook.exe hasn't so much to filter.

with kind regards

günter strubinsky

p.s. this is a personal and private opinion not to be mis-associated with
this newsgroup!

> -----Original Message-----
> From: [] On Behalf
> Of Edward Peschko
> Sent: Tuesday, 21 October, 2003 19:35
> To:
> Subject: Re: pwd option to return windows path
> > As has been previously pointed out, the point of cygwin is to present a
> > UNIX environment to users.  We do not go out of our way to modify every
> > executable in the distribution so that it provides an MS-DOS look and
> > feel for those who are not comfortable with UNIX path names.
> >
> > We've provided the cygpath utility, in true UNIX fashion, as a tool
> > for converting back and forth between windows and cygwin paths.  You can
> > use it or not.  We are not going to be changing pwd, ash, bash, tcsh,
> > ksh, and zsh to include cygpath options.
> >
> > While I fully appreciate that this may not satisfy your need to use
> > MS-DOS paths in the cygwin environment it it fully consistent with
> > the project goals.  I'd ask that you respect the goals rather than
> > consistently suggest that we should be making MS-DOS concessions.
> I'm not going to belabor the point, but this point of view makes -Mno-
> cygwin
> basically useless. And hence, any flag such as a MINGW mode impossible.
> In order to use it effectively, every single module/item that is ported to
> mingw expects to see certain behaviors, as generated by the msys tools.
> One example
> was uname, here's another example - pwd. Like it or not, msys and mingw
> are connected
> at the hip, and the more modules I compile, the more I see this.
> It is not reasonable to expect people to port their code both to mingw
> *and*
> -Mno-cygwin. And since mingw is connected to win32 far more than cygwin,
> people will
> port to mingw in greater numbers.
> If you want to discuss this, then we can do it in private. Your request
> that I
> only discuss 'certain things', in 'certain boundaries' is not fair, and
> I won't do it. If you disagree with what I post, please ignore it.
> But at the same time, I don't want to start another huge flame war, so
> talk to me
> offline if you feel strong enough about it.
> Ed
> --
> Unsubscribe info:
> Problem reports:
> Documentation:
> FAQ:         

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]