Your first command used your Windows installation of Python, not Cygwin's.
But it looks like you caught that.
To your question about upgrading pip in Cygwin, it's not usually a good
idea to overwrite any distro-provided packages. That's true on Linux and on
Cygwin as well.
But if you want access
Do you get the same behavior when you run dd with iflag=fullblock? Without
that flag, it's possible dd's input to read a smaller block than requested
(which would correspond with a smaller write to the output).
On Tue, Jun 23, 2020 at 9:28 AM Hashim Aziz via Cygwin
wrote:
> I hadn't checked with
.bat files - I just wanted to
illuminate that making Windows paths illegal is likely to break a
whole bunch of users' scripts, and really offers no benefit.
On Wed, Aug 5, 2015 at 5:14 PM, Andrey Repin wrote:
> Greetings, Nicholas Clark!
>
>> I totally agree that setting HOME to
I totally agree that setting HOME to a relative-path is probably a Bad
Idea, and can/should be undefined behavior. As for absolute paths (and
whether they should be POSIX, Windows, or either), that's a little
less cut and dry for me.
I currently use a ton of scripts of the general form:
Hi all,
I remember seeing a bunch of traffic on the subject of rebasing a few
years ago, with people saying that it wouldn't be necessary once we
moved over to 64-bit Cygwin. Did that wind up being true?
I've got some in-house tools that some of our developers want to use
on Cygwin, and I've been
ystems is
that SEGVs and other failures can cause windows to pop up some sort of
dialogue box, causing the batch test system to stall.
Nicholas Clark
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http
6 matches
Mail list logo
