Re: problem using recursive grep (-r option)

On 8/7/2012 1:55 PM, Sean Daley wrote: On Tue, Aug 7, 2012 at 11:08 AM, AngusC <> wrote: If I use the command: grep -nH -r "my pattern" *.* I get results back as expected But if the file pattern is like this: grep -nH -r "my pattern" *.log I get no results back (Even though I have a ton of

[g++] problem with xdigit for wide ctype facet

The attached program (main.cpp) demonstrates a problem with the wide-character support in cygwin's implementation of the standard C++ iostreams. The wide std::ctype facet should return true for ctype::is(std::ctype_base::xdigit, CH) for CH [0-9a-fA-F], but it only returns true for [0-9]. The narrow

Re: Fw: perl-libwin32 v. 0.28-3 installation fails with cryptic error message & crashes setup.exe

On 8/7/2012 2:17 PM, Oren Cheyette wrote: When attempting to update cygwin package perl-libwin32 I get an error message (dialog box) "Package file perl-libwin32 has a corrupt local copy, please remove and retry." at which point setup exits. So setup.exe didn't crash. It told you what to do an

Re: problem using recursive grep (-r option)

On Tue, Aug 7, 2012 at 11:08 AM, AngusC <> wrote: > > If I use the command: > > grep -nH -r "my pattern" *.* > > I get results back as expected > > But if the file pattern is like this: > > grep -nH -r "my pattern" *.log > > I get no results back (Even though I have a ton of files with this pattern

Re: cygwin 1.7.15: svn disk I/O error

On 8/6/2012 7:21 PM, Warren Young wrote: > Some time after *that*, at a future time entirely up to the Subversion > packages' maintainer, David Rothenberger, Subversion will be rebuilt > against those new SQLite packages. Is that actually necessary? SVN is dynamically linked to SQLite, so a recomp

Re: problem using recursive grep (-r option)

On 8/7/2012 7:15 PM, AngusC wrote: do not top post Why would I use find . -name "*.log" -exec grep -nH "my pattern" \{\} \; which is much longer to type when I can use grep ... -r ??? because it works ? But if the file pattern is like this: grep -nH -r "my pattern" *.log I get no re

Re: problem using recursive grep (-r option)

Why would I use find . -name "*.log" -exec grep -nH "my pattern" \{\} \; which is much longer to type when I can use grep ... -r ??? marco atzeri-4 wrote: > > On 8/7/2012 5:08 PM, AngusC wrote: >> >> If I use the command: >> >> grep -nH -r "my pattern" *.* >> >> I get results back as expected

Re: CygWin SVN should identify as CygWin

Greetings, Jochen Wiedmann! > I don't know about "more general". However, I know very well that > there's a particular project (Maven Release Plugin), which has this very > problem with svn, Then this is problem of Maven. Subversion libraries supposed to be linked directly, not used through "svn

Re: problem using recursive grep (-r option)

On 8/7/2012 5:08 PM, AngusC wrote: If I use the command: grep -nH -r "my pattern" *.* I get results back as expected But if the file pattern is like this: grep -nH -r "my pattern" *.log I get no results back (Even though I have a ton of files with this pattern with .log file extension). Am

RE: problem using recursive grep (-r option)

AngusC wrote: >If I use the command: > >grep -nH -r "my pattern" *.* > >I get results back as expected > >But if the file pattern is like this: > >grep -nH -r "my pattern" *.log > >I get no results back (Even though I have a ton of files with this pattern >with .log file extension). > >Am I doing s

Re: Ctrl+C not working with windows programs in Cygwin 1.7.16

On Aug 7 18:21, Andrey Repin wrote: > Greetings, Corinna Vinschen! > > >> But I still need to see a practical example of > >> running a M$ program like ping and stopping it with Ctrl+C > >> without CMD (or another shell). > > > Why don't you just try it? On W7: > > Start Menu ->> Run... -> Ent

Re: CygWin SVN should identify as CygWin

On 8/7/2012 10:16 AM, Jochen Wiedmann wrote: And, besides, your proposed solution won't work: I could, of course, use "which", or "where" to deduce the location of "svn", but what would that tell me. Assuming, I get "/usr/bin/svn", then I'd know that "which" is a CygWin binary (because it emits a

problem using recursive grep (-r option)

If I use the command: grep -nH -r "my pattern" *.* I get results back as expected But if the file pattern is like this: grep -nH -r "my pattern" *.log I get no results back (Even though I have a ton of files with this pattern with .log file extension). Am I doing something wrong? -- View th

RE: CygWin SVN should identify as CygWin

Jochen Wiedmann wrote: >On 07.08.2012 13:15, Adam Dinwoodie wrote: >> This isn't Subversion's responsibility; the problem is more general: how do >> you >> tell if the version of awk, sed or vim are Cygwin ones or not (or ones >> compiled >> containing a specific patch, or built on a particular d

Re: Cygwin IRC (Was: bash: loadable builtins)

On Tue, Aug 07, 2012 at 08:42:53AM +, Adam Dinwoodie wrote: >Yaakov (Cygwin/X) wrote: >>As there was a question on this in IRC tonight ... > >I hadn't realized there was a Cygwin IRC channel. A quick Google >around found me , >but I wouldn't h

Re: Ctrl+C not working with windows programs in Cygwin 1.7.16

Greetings, Corinna Vinschen! >> But I still need to see a practical example of >> running a M$ program like ping and stopping it with Ctrl+C >> without CMD (or another shell). > Why don't you just try it? On W7: Start Menu ->> Run... -> Enter "ping -t cygwin.com" -> Start Task Manager ->> Obser

Re: CygWin SVN should identify as CygWin

Greetings, Jochen Wiedmann! >> To all extents and purposes, Cygwin SVN behave just the way I'd expect >> from it. > I didn't say, it behaves wrong. My point is that I need to know that I > am using it, and not another svn, if all I know is "there's a svn binary > in my path". For what reason?

Re: CygWin SVN should identify as CygWin

On 07.08.2012 13:15, Adam Dinwoodie wrote: This isn't Subversion's responsibility; the problem is more general: how do you tell if the version of awk, sed or vim are Cygwin ones or not (or ones compiled containing a specific patch, or built on a particular day, or any other of a myriad of differ

Re: bash: loadable builtins

On 08/07/2012 01:37 AM, Yaakov (Cygwin/X) wrote: > Eric, > > As there was a question on this in IRC tonight, it is possible to make > bash loadable builtins work on Cygwin. Awesome! Thanks for the tips, and now I really need to find an excuse to make the time for a refresher release of bash for

Re: cygwin 1.7.15: svn disk I/O error

Christopher, On Tue, Aug 7, 2012 at 12:07 AM, Christopher Faylor wrote: >>Is the snapshot that cgf is testing going to roll back svn to SQLite >>3.7.3? > > Huh? No. I really have to point out that the Cygwin DLL != SQLite? I'm not familiar with the snapshot process, and I didn't realize from yo

Re: cygwin 1.7.15: svn disk I/O error

On Mon, Aug 6, 2012 at 10:21 PM, Warren Young wrote: >>> What reason could there be for a new Cygwin DLL to be accompanied by a >>> new >>> version of SQLite? Their maintainerships are entirely decoupled. >> >> Pardon my ignorance; I'm not familiar with the release process. > > Well, to a first a

Re: NASM package update

On 8/7/2012 1:06 PM, Diego Biurrun wrote: On Mon, Aug 06, 2012 at 08:48:47PM +0200, Diego Biurrun wrote: The NASM package in Cygwin is getting a tad long in the tooth. There is NASM 2.08.02 available, but 2.10.03 is current, i.e. NASM has done two major releases in the meantime. The package f

RE: CygWin SVN should identify as CygWin

Jochen Wiedmann wrote: >I didn't say, it behaves wrong. My point is that I need to know that I >am using it, and not another svn, if all I know is "there's a svn binary >in my path". This isn't Subversion's responsibility; the problem is more general: how do you tell if the version of awk, sed or

Re: NASM package update

On Mon, Aug 06, 2012 at 08:48:47PM +0200, Diego Biurrun wrote: > > The NASM package in Cygwin is getting a tad long in the tooth. There is > NASM 2.08.02 available, but 2.10.03 is current, i.e. NASM has done two > major releases in the meantime. The package for Cygwin was created > over two year

Re: Race condition that leads to random crashes in cygwin-based builds.

On Aug 7 Corinna Vinschen wrote: >On Aug 6 19:31, Andrey Khalyavin wrote: >> 2012/8/6 Corinna Vinschen wrote: >> > Andrey? >> > >> > On Jul 24 15:57, Corinna Vinschen wrote: >> >> On Jul 24 17:25, Andrey Khalyavin wrote: >> >> > Hi, we have build bots that crash randomly on Windows XP and rarely o

Re: Ctrl+C not working with windows programs in Cygwin 1.7.16

On Aug 7 12:06, marco atzeri wrote: > On 8/7/2012 10:20 AM, Andrey Repin wrote: > >Greetings, marco atzeri! > > > >>a "windows console terminal" is cmd.exe, IMHO. > > > >No. > > > >>There are no other console in windows as standard installation. > > > >You're confusing terminal with shell. > >CMD.

Re: CygWin SVN should identify as CygWin

On 07.08.2012 12:27, Andrey Repin wrote: To all extents and purposes, Cygwin SVN behave just the way I'd expect from it. I didn't say, it behaves wrong. My point is that I need to know that I am using it, and not another svn, if all I know is "there's a svn binary in my path". Jochen   S

Re: CygWin SVN should identify as CygWin

Greetings, Jochen Wiedmann! > On 07.08.2012 11:45, marco atzeri wrote: >> I do not understand why you need different file for cygwin. > You gave the answer just below, Marco: >> Commit on cygwin should follow cygwin rules (unix like), >> so something like I don't get this topic. At all. And i'm

Re: Ctrl+C not working with windows programs in Cygwin 1.7.16

On 8/7/2012 10:20 AM, Andrey Repin wrote: Greetings, marco atzeri! a "windows console terminal" is cmd.exe, IMHO. No. There are no other console in windows as standard installation. You're confusing terminal with shell. CMD.EXE is a shell, same as BASH. Console is a ... well, console. -

Re: CygWin SVN should identify as CygWin

On 07.08.2012 11:45, marco atzeri wrote: I do not understand why you need different file for cygwin. You gave the answer just below, Marco: Commit on cygwin should follow cygwin rules (unix like), so something like   SAG Consulting Services GmbH - Sitz/Registered office: Uhlandstraße 9,

Re: CygWin SVN should identify as CygWin

On 8/7/2012 10:16 AM, Jochen Wiedmann wrote: Hi, I apologize if I didn't pick the proper mailing list, but "discussion about packages" sounded right to me... wrong mailing list. Packages is for discussion between package managers, not for bugs or help. Forwarded to the right one: cygwin f

Cygwin IRC (Was: bash: loadable builtins)

Yaakov (Cygwin/X) wrote: >As there was a question on this in IRC tonight ... I hadn't realized there was a Cygwin IRC channel. A quick Google around found me , but I wouldn't have thought to do that without Yaakov's email. Is it's existance someth

Re: Ctrl+C not working with windows programs in Cygwin 1.7.16

Greetings, marco atzeri! > a "windows console terminal" is cmd.exe, IMHO. No. > There are no other console in windows as standard installation. You're confusing terminal with shell. CMD.EXE is a shell, same as BASH. Console is a ... well, console. -- WBR, Andrey Repin (anrdae...@freemail.ru)

Re: HOME directory has somehow been overridden

Greetings, Soumya Roy! Please, don't top-post. > Howver as it turns out, previously when I was typing "$ ls ~"I was > getting the contents of "Documents and Settings/Valnt"but now > however "$ ls ~" gives me the actual proper content of > "/cygwin/home/Valnt"which is perfect...howev

bash: loadable builtins

Eric, As there was a question on this in IRC tonight, it is possible to make bash loadable builtins work on Cygwin. 1) In src_compile(), add LOCAL_LDFLAGS='-Wl,--export-all,--out-implib,lib$(@:.exe=.dll.a)' to the final cygmake command. 2) In src_install(), add the following immediately after cy

Re: cygwin 1.7.15: svn disk I/O error

On 8/6/2012 11:06 PM, Achim Gratz wrote: Warren Young writes: I think I've given Achim Gratz enough time to try and fix the bug resulting from his build option changes. I cannot fix something that I can't even reproduce. I gave you some ideas of ways to reproduce it without TortoiseSVN. Did