sitory now that is compatible with Windows 7 and useable
for
> > installing Cygwin in anticipation of the upcoming loss of support.
>
> As these milestones occur I will make notes in the Cygwin Time Machine
> concerning the ending release snapshot and installers, like what I have
Corinna , thank you for the heads up regarding subsequent updates wrt Window
7.
Would it be possible to create a short "how-to" for installing the most
recently "known-to-work-with-Windows-7" version of Cygwin (presuming that
old versions remain accessible indefinitely...). Alternately, how one
> Here's a wondering: Could it have to do with line endings? If Windows
> CRLF is getting in there, then the variables might get a CR in them,
> which might do weird things. This assumes those are string variables,
> not numeric.
[Michel LaBarre] Better yet, how about an example using ma
Thank you for the thoughtful responses Michael and Marco.
I am sorting through the references from both of you while trying to keep in
mind
all the caveats regarding mount mode, file-path syntax ( /d/zot vs d:\zot ),
and whether
any given utility is "line" oriented or not to infer how it might
> -Original Message-
> From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On
> Behalf Of Soegtrop, Michael
> Sent: June 15, 2018 11:11 AM
> To: tuyanyi; cygwin
> Subject: RE: 2.10.0: Cygwin now can not work well with a file in dos format.
>
> Dear Tuyanyi,
>
> what has
If you need a boot environment that knows your hardware, try downloading the
backup program Reflect from Macrium - there is a free version.
(I use it for backup/recovery of my Win 10 and Win 7 systems. So far it has
been 100% solid.)
You can then use it to build a boot USB with all your
L A Walsh,
Please forgive the following naïve points but since I saw no mention of the
easy checks...
Did you do a "chkdsk" and "sfc /scannow" at any point to pare out any obvious
corruptions?
(When you chkdsk on C:, you will be asked if you want to do it on reboot since
the disk must be
Run it in bash instead.
^ is a quote character in CMD.
> -Original Message-
> From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On
> Behalf Of Dmitry Lanin
> Sent: May 4, 2018 4:32 PM
> To: cygwin@cygwin.com
> Subject: Bug: grep does not work with [^...]
>
> Bug: grep does
> -Original Message-
> From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On
> Behalf Of Corinna Vinschen
> Sent: March 5, 2018 2:55 PM
> To: cygwin@cygwin.com
> Subject: Re: sed seems to force UC filename on Mixed 8.3 filenames on
> FAT32
>
> On M
> -Original Message-
> From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On
> Behalf Of Corinna Vinschen
>
> On Mar 5 11:42, Michel LaBarre wrote:
> >
> > > Behalf Of Fergus Daly
> > > Starting to look exactly like that. On Windows
> -Original Message-
> From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On
> Behalf Of Fergus Daly
> Sent: March 5, 2018 4:06 AM
> To: The Cygwin Mailing List
> Subject: Re: sed seems to force UC filename on Mixed 8.3 filenames on
> FAT32
>
> >> ..."or operation on FAT32
> Subject: Possible output redirect bug
>
> Error output is not suppressed:
>
>
> $ cygstart cmd /c "( >&2 pause ) >> test.txt"
>
> $ cat /dev/null >> test.txt >/dev/null 2>&1
> bash: test.txt: Device or resource busy
The error message is not from the process running "cat" which is to what
e CYGWIN audience for whom strict POSIX compliance is secondary and
the main objective is to have useful tools under Windows that also support
portability outside Windows. Thank you.
Michel LaBarre
> --
> cyg Simple
>
> --
> Problem reports: http://cygwin.com/problems.htm
U bash, version 4.4.12(3)-release (x86_64-unknown-cygwin)
By the way, the "s" set option ($- above) is not defined in the bash
reference manual that I have and is not accepted
by the "set" built into bash so I don't know how it gets set. (i.e."set -s
s" or &
com] On
> Behalf Of Duncan Roe
> Sent: August-21-17 6:56 PM
> To: cygwin@cygwin.com
> Subject: Re: alias appears to not work inside a called bash scripty
>
> On Mon, Aug 21, 2017 at 06:30:15PM -0400, Michel LaBarre wrote:
> > Hello all,
> >
> > I have a 4 line
sion, whether the
alias is explicitly defined in the session or in .bashrc.
Thank you in advance for any insights.
BTW - I just re-subscribed to cygwin 4-5 hours ago and have not seen any
mail which seems unusual based on past experience.
Michel LaBarre
613-692-0507
cygcheck.out
Description:
> -Original Message-
> From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On
> Behalf Of Greg Freemyer
> Sent: December-07-16 5:08 PM
> To: brian.ing...@systematicsw.ab.ca; cygwin@cygwin.com
> Subject: Re: permission question
>
> If I'm going to relegate rsync to the trash
Suggestion to Kipton:
od -cx
will show you exactly what is in your script so you can see any spurious
carriage-returns or other special characters.
> -Original Message-
> From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On
> Behalf Of Eric Blake
> Sent:
Based on the emails under this thread and other items I found, it seems that
anomalies
handling program suffixes within CYGWIN are not new. It has been proposed that
the
relevant code be re-thought. I suggest that any rethink consider PATHEXT
support.
It may be of no interest for CYGWIN
-Original Message-
From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On Behalf Of
Corinna Vinschen
Sent: August-08-16 10:33 AM
To: cygwin@cygwin.com
Subject: Re: PATHEXT is fundamental to Windows and Should be recognised by
CYGWIN
On Aug 8 09:43, cyg Simple wrote:
> On
Back-slashes pre-date Bill. Can't blame him for that one.
Before Bill Gates there was "CP/M" launched by Digital Research - basically a
bunch of nerd-hippies in Seattle. IBM was looking to license it for a low end
machine it was developing (ominous background music appropriate at this point).
Hello cygsimple,
Thanks for the advice regarding line length.
I will try to remember to rein in my margins when emailing to cygwin.
Thanks for your recognition of PATHEXT's potential value;
reassuring to know I am not alone in my delusions.
Regarding providing code, I am somewhat stale
ce Rice
Sent: August-04-16 1:40 AM
To: Cygwin Mailing List
Subject: Re: PATHEXT is fundamental to Windows and Should be recognised by
CYGWIN
> On Aug 3, 2016, at 8:43 PM, Michel LaBarre wrote:
>
> The CYGWIN site makes it quite difficult to discern how somebody can
> report an issue o
ate its adoption by both Unix and non-Unix types.
Cheers,
Michel
-Original Message-
From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On Behalf Of Kaz
Kylheku
Sent: August-03-16 10:55 PM
To: Michel LaBarre
Cc: cygwin@cygwin.com
Subject: Re: PATHEXT is fundamental to Windows
ments for which I used the MKS toolkit.
Michel LaBarre
--
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
25 matches
Mail list logo