When I execute "Find in Files", a console windows pops up for a fraction of a second, and then disappears. No results being shown, also no error message.
The "message" line of Geany shows:
grep -nHlrF -- ....
The only grep.exe in my PATH is the Cygwin implementation of grep. This should work well, and even if there is a problem with my grep, I wonder why I don't see any error message.
Ronald
On 16 March 2012 23:01, Fischer, RonaldX O ronaldx.o.fischer@intel.com wrote:
When I execute "Find in Files", a console windows pops up for a fraction of a second, and then disappears. No results being shown, also no error message.
The "message" line of Geany shows:
grep -nHlrF -- ....
The only grep.exe in my PATH is the Cygwin implementation of grep. This should work well, and even if there is a problem with my grep, I wonder why I don't see any error message.
Please always specify version and platform when asking questions.
Does the grep command work with those options if you try it on the command line in the appropriate directory?
Anything grep outputs should be shown, so perhaps it doesn't return anything, including an error message.
Unfortunately some more user friendly completion processing is available in Unix, but Windows does not provide the same completion statuses.
Cheers Lex
Ronald
Geany mailing list Geany@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany
On 16 March 2012 23:01, Fischer, RonaldX O ronaldx.o.fischer@intel.com wrote:
When I execute "Find in Files", a console windows pops up for a
fraction of a second, and
then disappears. No results being shown, also no error message.
The "message" line of Geany shows:
grep -nHlrF -- ....
The only grep.exe in my PATH is the Cygwin implementation of grep.
This should work well, and
even if there is a problem with my grep, I wonder why I don't see any
error message.
Please always specify version and platform when asking questions.
Geany: 0.21 Platform: Windows 7 (64bit)
Does the grep command work with those options if you try it on the command line in the appropriate directory?
Yes. It returns a list of filenames which matched.
Anything grep outputs should be shown, so perhaps it doesn't return anything, including an error message.
There is some output - I can see it while the console Windows is flashing open -, but the time is to short to read it.
Unfortunately some more user friendly completion processing is available in Unix, but Windows does not provide the same completion statuses.
No, but in this case, I don't see why Geany should not be able to start grep. I even configured it by specifying the complete path (C:\Cygwin\bin\grep.exe) of the grep command - same effect.
Ronald
On 16 March 2012 23:52, Fischer, RonaldX O ronaldx.o.fischer@intel.com wrote:
On 16 March 2012 23:01, Fischer, RonaldX O ronaldx.o.fischer@intel.com wrote:
When I execute "Find in Files", a console windows pops up for a
fraction of a second, and
then disappears. No results being shown, also no error message.
The "message" line of Geany shows:
grep -nHlrF -- ....
The only grep.exe in my PATH is the Cygwin implementation of grep.
This should work well, and
even if there is a problem with my grep, I wonder why I don't see any
error message.
Please always specify version and platform when asking questions.
Geany: 0.21 Platform: Windows 7 (64bit)
Does the grep command work with those options if you try it on the command line in the appropriate directory?
Yes. It returns a list of filenames which matched.
Anything grep outputs should be shown, so perhaps it doesn't return anything, including an error message.
There is some output - I can see it while the console Windows is flashing open -, but the time is to short to read it.
Unfortunately some more user friendly completion processing is available in Unix, but Windows does not provide the same completion statuses.
No, but in this case, I don't see why Geany should not be able to start grep. I even configured it by specifying the complete path (C:\Cygwin\bin\grep.exe) of the grep command - same effect.
Well, clearly it is starting it, the command window shows that.
But it shouldn't run in a command window AFAIK, the output should go to Geany, its not much good going to a window which, as you say, only hangs around for a moment.
Geany just calls a Glib routine to run the command, what version of Glib are you using? see in Help->Debug Messages
Cheers Lex
Ronald _______________________________________________ Geany mailing list Geany@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany
On 16/03/2012 12:01, Fischer, RonaldX O wrote:
The only grep.exe in my PATH is the Cygwin implementation of grep. This should work well, and even if there is a problem with my grep, I wonder why I don't see any error message.
That is likely the problem. GLib's spawning on Windows doesn't work with everything. Try using grep from:
On 12-03-16 09:09 AM, Nick Treleaven wrote:
On 16/03/2012 12:01, Fischer, RonaldX O wrote:
The only grep.exe in my PATH is the Cygwin implementation of grep. This should work well, and even if there is a problem with my grep, I wonder why I don't see any error message.
That is likely the problem. GLib's spawning on Windows doesn't work with everything. Try using grep from:
I thought Geany used CreateProcess() or some such from the win32 API for this stuff? If not, maybe we could switch this code to use utils_spawn* so that it does?
Cheers, Matthew Brush
On 17/03/2012 03:17, Matthew Brush wrote:
On 12-03-16 09:09 AM, Nick Treleaven wrote:
On 16/03/2012 12:01, Fischer, RonaldX O wrote:
The only grep.exe in my PATH is the Cygwin implementation of grep. This should work well, and even if there is a problem with my grep, I wonder why I don't see any error message.
That is likely the problem. GLib's spawning on Windows doesn't work with everything. Try using grep from:
I thought Geany used CreateProcess() or some such from the win32 API for this stuff? If not, maybe we could switch this code to use utils_spawn* so that it does?
Find in Files uses GLib's async spawn, which doesn't work for some tools IME.
Build/run commands use a synchronous Windows call which works but is not asynchronous as it is supposed to be and so adds complexity to the code.
We really need an asynchronous spawn that works properly on Windows. We could make FIF use the synchronous Windows spawn code, causing a delay on large directories/recursion, but again the code to do this would be messy as sync vs async are fundamentally different.
Regards, Nick