public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: Evgeny Grin <k2k@yandex.ru>, cygwin@cygwin.com
Subject: Re: Windows Subsystem for Linux starts to compete with Cygwin?
Date: Sat, 29 Oct 2016 06:24:00 -0000	[thread overview]
Message-ID: <1276132483.20161028232057@yandex.ru> (raw)
In-Reply-To: <0b3de073-1be5-248b-19b3-26827947607e@yandex.ru>

Greetings, Evgeny Grin!

> On 27.10.2016 16:22, Andrey Repin wrote:
>> Greetings, Evgeny Grin!
> Privet, Андрей!

>>> With latest Window Insider preview it's possible to run Linux command
>>> from cmd, Windows commands from bash and even use input-output redirects!
>>> https://blogs.msdn.microsoft.com/wsl/2016/10/19/windows-and-ubuntu-interoperability/
>>> Seems that WSL also automatically translate \r\n<->\n.
>> 
>> Which will break a lot of tools not expecting this kind oh "help".

> A lot of?
> I don't know many... correction.. any GNU/Linux tools that works badly
> with \n newlines.

I was specifically referring to unexpected conversion, if you didn't notice.

>>> Is Cygwin still better for something?
>> 
>> Did they fixed the user mappings?

> I don't know as I didn't have any problem with it.

As long as you're only user, you won't see it, but try to use it in a
multiuser environment.
Previously, it was not possible.

>>> I understand that WSL and Cygwin are completely different approaches,
>>> but from user perspective both are kind of sets of GNU/Linux commands
>>> and both are using some intermediate layer (cygwin1.dll or LXSS).
>> 
>> WSL requires Windows 10. End of story.

> Do you mean, that Windows itself is a problem?
> Or version 10 of Windows is a problem? Anyway, all Windows users will
> use Windows 10 (or successors) sooner or later.
> So it's only the beginning of the story.

This is the same argument I hear over and over again. "suck it up, there's no
other choice".
There is other choice.



-- 
With best regards,
Andrey Repin
Friday, October 28, 2016 23:14:23

Sorry for my terrible english...

  reply	other threads:[~2016-10-28 20:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-26 22:59 Evgeny Grin
2016-10-27  1:04 ` Duncan Roe
2016-10-27 14:46   ` Evgeny Grin
2016-10-27 17:10   ` Erik Soderquist
2016-10-27 14:42 ` Andrey Repin
2016-10-27 15:32   ` Evgeny Grin
2016-10-29  6:24     ` Andrey Repin [this message]
2016-10-29 17:16     ` L. A. Walsh
2016-10-29 18:18       ` Brian Inglis
2016-10-31 14:52       ` Andrey Repin

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=1276132483.20161028232057@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --cc=cygwin@cygwin.com \
    --cc=k2k@yandex.ru \
    /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).