A new release of grep, 3.0-1, has been uploaded and will soon reach a
mirror near you; leaving the previous version at 2.27-2.
NEWS:
=
This is a new upstream release. For more details on grep, see
the documentation in /usr/share/doc/grep/.
DESCRIPTION:
GNU Grep searches one or m
On 11/02/2017 00:05, Eliot Moss wrote:
> On 2/10/2017 6:50 PM, Sam Edge wrote:
>
>> Sorry, did anyone actually read Andrey's post?
>
> Yes, but I was going through the emails in order and responded
> to the earlier one before I got to the later one. Sorry to have
> added noise to the list ...
>
No
On 2/10/2017 6:50 PM, Sam Edge wrote:
Sorry, did anyone actually read Andrey's post?
Yes, but I was going through the emails in order and responded
to the earlier one before I got to the later one. Sorry to have
added noise to the list ...
EM
--
Problem reports: http://cygwin.com/prob
On 10/02/2017 23:17, Eliot Moss wrote:
> On 2/10/2017 3:03 PM, Gluszczak, Glenn wrote:
>> * is a legal character for ls but perhaps not cygpath? I don't know.
>> No files or directories are using * in the name.
>>
>> Not sure about incorrect terminal settings as I never touched any.
>> It shows up
On 2/10/2017 3:03 PM, Gluszczak, Glenn wrote:
* is a legal character for ls but perhaps not cygpath? I don't know.
No files or directories are using * in the name.
Not sure about incorrect terminal settings as I never touched any.
It shows up in mintty and ssh equally. The characters that appea
On Fri, Feb 10, 2017 at 1:34 PM, Andrey Repin wrote:
> Greetings, Gluszczak, Glenn!
>
>> * is a legal character for ls but perhaps not cygpath?
>
> "*" is not a legal path name character. And cygpath expects a path.
AFAICT, '*' is a legal character in a filename or directory name on
Posix systems
On Fri, Feb 10, 2017 at 1:46 PM, Gluszczak, Glenn wrote:
> I suppose the glob explanation from Michael explains this behavior in sh.
> Though unsupported, it seems to work (probably some side cases do not).
It seems to me that the behavior is supported and working. Bash or sh
takes an unescaped ar
I suppose the glob explanation from Michael explains this behavior in sh.
Though unsupported, it seems to work (probably some side cases do not).
$ cygpath -w /usr/bin/*
C:\cygwin64\bin\[.exe
C:\cygwin64\bin\2to3
C:\cygwin64\bin\addftinfo.exe
C:\cygwin64\bin\addr2line.exe
C:\cygwin64\bin\whatis.ex
Greetings, Gluszczak, Glenn!
> * is a legal character for ls but perhaps not cygpath?
"*" is not a legal path name character. And cygpath expects a path.
> I don't know.
> No files or directories are using * in the name.
See above.
> Not sure about incorrect terminal settings as I never touch
Marco,
Thanks VERY much for explaining I have a BLODA interference issue and
suggesting I try using safe mode--I did, and now I have a complete
Cygwin installation. I still have to work on the "fork: retry:
Resource temporarily unavailable" issue, which I may not be able to
resolve, but you've ena
Thanks for the explanation. Just odd how cmd.exe only sometimes misbehaves.
%%%cygpath -w /usr/a/b/*
C:\cygwin\usr\a\b\
%%%cygpath -w /a/b/*
C:\cygwin\a\b\
%%%cygpath -w /a/b/c/*
C:\cygwin\a\b\c\
-Original Message-
From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On Beh
On Fri, Feb 10, 2017 at 12:42 PM, Michael Enright wrote:
> On Fri, Feb 10, 2017 at 12:31 PM, Gluszczak, Glenn wrote:
>> Sorry, I forgot the user I log in as is switching to cmd.exe.
>>
>> This doesn't happen in sh or tcsh, so it is probably a non-issue.
>>
>
> My results are from running a "normal"
On Fri, Feb 10, 2017 at 12:31 PM, Gluszczak, Glenn wrote:
> Sorry, I forgot the user I log in as is switching to cmd.exe.
>
> This doesn't happen in sh or tcsh, so it is probably a non-issue.
>
My results are from running a "normal" bash-under-mintty setup.
If I go to a cmd.exe window and start b
On Fri, Feb 10, 2017 at 11:36 AM, Andrey Repin wrote:
> Greetings, Gluszczak, Glenn!
>
>> Isn’t this a defect in cygpath? Looks like memory corruption.
>
>> %%%cygpath -w /usr/non-existent/*
>> C:\cygwin\usr\non-existent\�[W��
>
> Looks more like private character space combined with incorrect te
Sorry, I forgot the user I log in as is switching to cmd.exe.
This doesn't happen in sh or tcsh, so it is probably a non-issue.
-Original Message-
From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On Behalf Of
Gluszczak, Glenn
Sent: Friday, February 10, 2017 3:04 PM
To: cy
* is a legal character for ls but perhaps not cygpath? I don't know.
No files or directories are using * in the name.
Not sure about incorrect terminal settings as I never touched any.
It shows up in mintty and ssh equally. The characters that appear vary.
Some non-existent paths do *not* pro
Greetings, Gluszczak, Glenn!
> Isn’t this a defect in cygpath? Looks like memory corruption.
> %%%cygpath -w /usr/non-existent/*
> C:\cygwin\usr\non-existent\�[W��
Looks more like private character space combined with incorrect terminal setup.
See
http://cygwin.com/cygwin-ug-net/using-specia
Isn’t this a defect in cygpath? Looks like memory corruption.
%%%cygpath -w /usr/tmp/*
C:\cygwin\usr\tmp\
%%%cygpath -w /usr/non-existent/*
C:\cygwin\usr\non-existent\�[W��
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
New version 2.2.2-1 of
lyx
is available in the Cygwin distribution:
CHANGES
Last upstream release.
http://www.lyx.org/announce/2_2_2.txt
DESCRIPTION
LyX is a document processor that encourages an approach to writing
based on the structure of your documents (WYSIWYM) and not simply
their appe
Hans-Bernhard Bröker skrev:
Am 03.02.2017 um 12:49 schrieb Thomas Nilefalk:
Hans-Bernhard Bröker skrev:
Am 02.02.2017 um 22:12 schrieb Thomas Nilefalk:
'how can I make a 32-bit compiled cygwin program run under cygwin64'?
You can't. Nor can anybody else. For a Cygwin64-based program,
Cyg
20 matches
Mail list logo
