Re: problem using recursive grep (-r option)
On 7 August 2012 16:57, marco atzeri 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
>>
>> 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?
>>
>
> in the second case the "-r" is looking for *.log
> file or directories and I guess the directory does not match.
>
> Try
>
> find . -name "*.log" -exec grep -nH "my pattern" \{\} \;
Or have a look at grep's --include option.
Andy
--
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
Re: problem using recursive grep (-r option)
I did try the --include way but in Cygwin it didn't work for some reason.
Neither does
find "." -name "*.log" -exec grep -nH "my pattern" {} \;
or
find "." -name "*.log" | grep -nH "my pattern"
So struggling about on Cygwin at the moment.
Sean Daley-2 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 files with this
>> pattern
>> with .log file extension).
>>
>> Am I doing something wrong?
>> --
> The first one works because *.* will match everything your current
> directory,
> including sub-directories and it will recurse through each of them. The
> second example will first match anything in your current directory with a
> .log
> extension and try to grep it (if it's a file) or recurse through it if
> it's a directory.
>
> What I believe you want to do (at least works on Linux) is
> grep -nH -r "my pattern" --include "*.log" .
>
> Sean
>
> --
> 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
>
>
>
--
View this message in context:
http://old.nabble.com/problem-using-recursive-grep-%28-r-option%29-tp34266659p34270643.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
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
Re: problem using recursive grep (-r option)
This works
find . -name "*.log" | grep -nH -r "my pattern" *.*
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
>>
>> 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?
>>
>
> in the second case the "-r" is looking for *.log
> file or directories and I guess the directory does not match.
>
> Try
>
> find . -name "*.log" -exec grep -nH "my pattern" \{\} \;
>
> Regards
> Marco
>
> --
> 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
>
>
>
--
View this message in context:
http://old.nabble.com/problem-using-recursive-grep-%28-r-option%29-tp34266659p34270681.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
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
Re: problem using recursive grep (-r option)
On 8/8/2012 11:11 AM, AngusC wrote:
DO NOT TOP POST !
I did try the --include way but in Cygwin it didn't work for some reason.
Neither does
find "." -name "*.log" -exec grep -nH "my pattern" {} \;
find "." -name "*.log" -exec grep -nH "my pattern" \{\} \;
--
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
Re: Please test snapshots
I'm at the August 7th snapshot now and Emacs just died on me with this message: > Connection lost to X server `:0.0' When compiled with GTK, Emacs cannot recover from X disconnects. This is a GTK bug: https://bugzilla.gnome.org/show_bug.cgi?id=85715 For details, see etc/PROBLEMS. The X server is still running as well as a number of other X applications. Regards, Achim. -- 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
Re: cygwin 1.7.15: svn disk I/O error
On 8/7/2012 11:32 AM, David Rothenberger wrote: 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 recompile isn't necessary unless the ABI for SQLite changes, right? I was just recalling your -3 and -4 packages, rebuilt after my last SQLite release, partly to see if rebuilding would fix the svn+sqlite problems. You are right that that might not have done anything, and that consequently a rebuild won't be necessary or helpful now either. -- 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
Re: CygWin SVN should identify as CygWin
On 07.08.2012 18:30, Andrey Repin wrote: Subversion libraries supposed to be linked directly, not used through "svn" command-line wrapper. For more details, go read http://svn-book.org/ Quite obviously, you never attempted to support a diverse user basis (just think of all the platforms) in Java (or another programming language) using C libraries. I don't think, it is required to point out the various problems. Suffice it to say, that historically the SVN Java bindings where the starting point for most projects integrating SVN into Java, but where dropped for a reason. Jochen SAG Consulting Services GmbH - Sitz/Registered office: Uhlandstraße 9, 64297 Darmstadt, Germany - Registergericht/Commercial register: Darmstadt HRB 85598 Geschäftsführer/Managing Directors: Klaus Katz, Arno Theiß - http://www.softwareag.com/ -- 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
[ANNOUNCEMENT] Updated: texlive-collection-basic-20120628-2 (TEST)
The following package is now available as a test release: *** texlive-collection-basic-20120628-2 This should fix the postinstall problems discussed here: http://cygwin.com/ml/cygwin-apps/2012-08/msg9.html http://cygwin.com/ml/cygwin-apps/2012-08/msg00013.html Please test it and report any problems to the Cygwin mailing list. It would be especially helpful if you would look at /var/log/setup.log.full after installing it, and make sure there are no errors involving updmap. If there are no problems, this will be promoted from "test" to "current" within a week or two. Ken Brown Cygwin's TeX Live maintainer *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at the above URL. -- 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
Re: problem using recursive grep (-r option)
On 2012-08-08, marco atzeri wrote:
> On 8/8/2012 11:11 AM, AngusC wrote:
> >
> DO NOT TOP POST !
>
> >I did try the --include way but in Cygwin it didn't work for some reason.
Both of these work fine for me in Cygwin (on Windows XP):
grep -nH -r "my pattern" --include "*.log" .
grep -nH -r "my pattern" --include=*.log .
> >Neither does
> >
> >find "." -name "*.log" -exec grep -nH "my pattern" {} \;
as does that
>
> find "." -name "*.log" -exec grep -nH "my pattern" \{\} \;
and that.
The quoting of . and {} is not needed.
Perhaps the real problem is with "my pattern".
Regards,
Gary
--
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
Re: CygWin SVN should identify as CygWin
On 8/7/2012 1:16 AM, Jochen Wiedmann wrote: > from what I can tell, a user of CygWin SVN has no possibilities to be > aware of the fact that it is indeed CygWin SVN, and not another program. > This is the root cause for problems like > >http://jira.codehaus.org/browse/SCM-213 As the volunteer Cygwin Subversion packager, I guess I should chime in here. I'm not going to customize the --version string to indicate SVN is Cygwin. I have no idea if other tools or scripts are parsing this, so I'm not going to make it different from what --version reports on all other platforms. As others have mentioned, there are several other solutions, such as looking at the output of "which svn". (If it says /usr/bin/svn, it's Cygwin.) It is also possible to do a functionality test, e.g. by looking at the output of "svn info /tmp". Another possibility is to use Subversion bindings instead of the CLI, as others have mentioned. For Java apps, there is also SVNKit, a 100% Java subversion library implementation. Regarding the problem with Maven you referenced, a better solution (and one suggested in the comments) is to add an option to Maven so one can configure which svn binary is used. Failing that, one can easily write a wrapper script for Maven that will put a native svn binary ahead of the Cygwin one in the path. -- David Rothenberger daver...@acm.org Ryan's Law: Make three correct guesses consecutively and you will establish yourself as an expert. -- 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
setup.exe and cntlm proxy
hi, does anybody use cntlm proxy with cygwin setup.exe? I have tried it and looks a bit strange. First of all, cntlm proxy with browser works fine, so does wget. With setup.exe works only if the proxy is in single thread mode (all request are serialized). Otherwise setup.exe gets stuck attempting to get mirrors.lst What is interesting, when I fire up wireshark, I can see mirrors.lst being received by cntlm. Cheers, Pawel -- 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
[ANNOUNCEMENT] Updated : netcdf-4.2.1.1-1
Versions netcdf-4.2.1.1-1 netcdf libnetcdf-devel libnetcdf7` are available in the Cygwin distribution: CHANGES - New upstream release The 4.2.1.1 release for the netCDF C libraries contains new features, bug fixes, performance improvements, and internal refactoring. It adds two patches to version 4.2.1 to fix bugs that significantly slowed remote access and that incorrectly displayed some netCDF-4 strings in the output of the ncdump utility. http://www.unidata.ucar.edu/software/netcdf/#netcdf_relnotes DESCRIPTION NetCDF (network Common Data Form) is a set of software libraries and machine-independent data formats that support the creation, access, and sharing of array-oriented scientific data. HOMEPAGE http://www.unidata.ucar.edu/software/netcdf/ Marco Atzeri If you have questions or comments, please send them to the cygwin mailing list at: cygwin (at) cygwin (dot) com . *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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
Windows clipboard and Emacs yank, kill-region, and kill-ring-save
I have updated my packages to the latest versions. I have long had installed - emacs - emacs-X11 - emacs-el - xemacs-emacs-common - X11 In Emacs, ^Y is the default keystroke for the basic "yank", to paste the contents of the most recently element of the kill ring (the text most recently cut or copied in Emacs). Until some time in the past few weeks, I am 80% sure that ^Y would grab out of the Windows clipboard -- that is, I could copy in Windows using ^C or Ctrl-Ins, and then use ^Y in Emacs to paste it. But I think that sometime in the last few weeks, perhaps with the end-of-July update of Emacs in Cygwin, it stopped working. Now, ^Y only pastes what was killed (or copied) in Emacs. Similarly, if I kill or copy text in Emacs, it's not put into the Window clipboard. Any Emacs users out there? Am I misremembering the old behavior? At home I use Linux, and there the X clipboard and Emacs clipboard usually work together (modulo X having more than one). If I'm not, did something change, and can I do some setting to obviate it in Emacs? -- Tim McDaniel, t...@panix.com -- 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
Re: Windows clipboard and Emacs yank, kill-region, and kill-ring-save
On 8/8/2012 4:49 PM, Tim McDaniel wrote:
I have updated my packages to the latest versions. I have long had
installed
- emacs
- emacs-X11
- emacs-el
- xemacs-emacs-common
- X11
In Emacs, ^Y is the default keystroke for the basic "yank", to paste
the contents of the most recently element of the kill ring (the text
most recently cut or copied in Emacs). Until some time in the past
few weeks, I am 80% sure that ^Y would grab out of the Windows
clipboard -- that is, I could copy in Windows using ^C or Ctrl-Ins,
and then use ^Y in Emacs to paste it.
But I think that sometime in the last few weeks, perhaps with the
end-of-July update of Emacs in Cygwin, it stopped working. Now, ^Y
only pastes what was killed (or copied) in Emacs. Similarly, if I
kill or copy text in Emacs, it's not put into the Window clipboard.
Any Emacs users out there?
Am I misremembering the old behavior? At home I use Linux, and there
the X clipboard and Emacs clipboard usually work together (modulo
X having more than one).
If I'm not, did something change, and can I do some setting to obviate
it in Emacs?
There have been some changes in how emacs handles selections, starting
with emacs-24.1. Look at the NEWS file ('C-h n') and search for
"selection changes". It describes the changes and tells you how to
restore the old behavior.
Ken
--
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
Re: Please test snapshots
On Mon, Aug 06, 2012 at 05:15:10PM -0700, Daniel Colascione wrote:
>On 8/6/2012 2:07 PM, Daniel Colascione wrote:
>> I just saw a hang building Emacs (using "make bootstrap")
>
>Signal handling appears to be broken. Here's a simple testcase. Run the program
>and hit control-c. It'll print "got Alarm clock", then stop accepting any
>signals at all, even SIGSTOP. The same program works fine on my Debian stable
>box.
I forgot to send out a notice about this.
This particular issue should be fixed in the latest snapshot.
You mention generic "signal handling" rather than "sigwaitinfo" so I don't
know if there are other issues. It doesn't seem like much would work if
signal handling was completely broken, though.
Thanks for the test case.
cgf
>#define _GNU_SOURCE 1
>#include
>#include
>#include
>#include
>#include
>
>int
>main()
>{
>sigset_t waitmask;
>int sig;
>
>sigemptyset (&waitmask);
>sigaddset (&waitmask, SIGINT);
>sigprocmask (SIG_BLOCK, &waitmask, NULL);
>
>for (;;) {
>sig = sigwaitinfo (&waitmask, NULL);
>fprintf (stderr, "got %s\n", sys_siglist[sig]);
>if (sig == SIGINT) {
>break;
>}
>}
>
>return 0;
>}
>
--
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
Re: Windows clipboard and Emacs yank, kill-region, and kill-ring-save
On Wed, 8 Aug 2012, Ken Brown wrote:
There have been some changes in how emacs handles selections,
starting with emacs-24.1. Look at the NEWS file ('C-h n') and
search for "selection changes". It describes the changes and tells
you how to restore the old behavior.
Yes! The important one for me is
(setq x-select-enable-primary t)
Thank you very much for the quick and informative answer!
--
Tim McDaniel, t...@panix.com
--
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
Re: Please test snapshots
On 8/8/2012 2:59 PM, Christopher Faylor wrote: > On Mon, Aug 06, 2012 at 05:15:10PM -0700, Daniel Colascione wrote: >> On 8/6/2012 2:07 PM, Daniel Colascione wrote: >>> I just saw a hang building Emacs (using "make bootstrap") >> >> Signal handling appears to be broken. Here's a simple testcase. Run the >> program >> and hit control-c. It'll print "got Alarm clock", then stop accepting any >> signals at all, even SIGSTOP. The same program works fine on my Debian >> stable box. > > I forgot to send out a notice about this. > > This particular issue should be fixed in the latest snapshot. The latest snapshot seems to fix the issue. > > You mention generic "signal handling" rather than "sigwaitinfo" so I don't > know if there are other issues. It doesn't seem like much would work if > signal handling was completely broken, though. Apologies --- I should have been more specific. No, I haven't noticed any other signal breakage aside from the sigwaitinfo problem and the Emacs build hang. I can't reproduce either with the new snapshot. signature.asc Description: OpenPGP digital signature
Re: problem using recursive grep (-r option)
Greetings, AngusC! > This works > find . -name "*.log" | grep -nH -r "my pattern" *.* What? This is ridiculous. Do you read what you write? -- WBR, Andrey Repin (anrdae...@freemail.ru) 09.08.2012, <10:27> Sorry for my terrible english... -- 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
Re: Please test snapshots
Achim Gratz NexGo.DE> writes: > The X server is still running as well as a number of other X applications. Something's wrong here with the new snapshot and signal handling / job control in conjunction with X and the newest snapshot... this morning the shell proclaimed (I left it running overnight) after the first command: [1] - Done gitk --all However, I have only started one gitk since starting X and it is still running. Regards, Achim. -- 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
