Re: [cssed-devel] cssed-findinfiles-plugin: some problems

[<mic...@ea...>]

Le 14 sept. 2004, =E0 14:50, Iago Rubio a =E9crit :
> On Tue, 2004-09-14 at 12:08, Mich=E8le Garoche wrote:
>> Le 14 sept. 2004, =E0 10:10, Iago Rubio a =E9crit :
>>> On Mon, 2004-09-13 at 21:39, Mich=E8le Garoche wrote:
>>>> Le 13 sept. 2004, =E0 15:08, Iago Rubio a =E9crit :
>>>> Besides, it will be a nice plus: you can search by selecting a word=20=

>>>> or
>>>> by entering a word in the search field, very useful when you want =
to
>>>> be
>>>> sure that a term does not exist in a file for example.
>>> You can do it right now. If you can't do it, it's a bug.
>>> Just type something in the search term entry and click "Find".
>> I only can do it if the base directory is set to the document's path.
> If it's not, use the menu "In file's base directory". This should set
> the base dir to the file's one, and search for the selected text.
No it does not set the base dir if there is no previous base dir set in=20=

the bottom panel.

>> What I mean here is when using the contextual menu in the document =
and
>> the search in file base's.
> Sorry but I'm misunderstunding you :)
> What you want is to search a yet used term - so in the search term=20
> entry
> - in the current file's base directory, isn't it ?
Not exactly, I want to be able to search in the current document with=20
the search term given in the search term entry in the bottom panel.

> If so I must add another menu item to the pop menu.
> Current ones:
> ->"In current base directory" - search for the selected text on=20
> document
> on the configured search base directory. Changes the text on the =
search
> term entry.
>
> ->"In file's base directory" - search for the selected text on the
> current document's base directory. Changes the text on the search term
> entry and in the base directory entry.
>
> Those could go to:
> Find in files -> Selected text -> "In current base directory"
> Find in files -> Selected text -> "In file's base directory"
>
> And add:
> ->"Search in file's base directory" - search for the configured search
> term in this file's base directory. Changes the base directory entry.
>
> So the final layout of this pop menu should be something like:
>
> Find In Files	-> "Search in file's base directory"
> 		-> Selected text -> "In current base directory"
> 		-> Selected text -> "In file's base directory"
>
> Quoted items are action widgets (will respond user's clicks).
>
> What do you think about that ??
This is another option, but it is not the same as I thought of. Maybe=20
it is more related to quicksearch plugin, now that I think about it.


>>> Does this command line freezes find (in a shell) ?
>>> find `pwd` -print0 -type f -maxdepth 1 | xargs -0 grep -n term
>> It seems too, already 10 minutes running, just because in the search
>> directory there is a pipe, and it freezes at this level.
> There's a bug here as `find -type -f` should discard named pipes.
I think the problem is -print0 seels ti discard -type f effect.

>> It reads ok up to .lyx, then freezes, but the ouput is not very=20
>> useful:
>> ...
>> grep: /Users/michga/.gconf: Operation not permitted
>> grep: /Users/michga/.gconfd: Operation not permitted
> Also here as`find -type f` should discard directories.
Same as above

> I must test your `find` binary to check why it doesn't works.
I know find is buggy on Mac OS X. Generally I search with:

find path -name regex | xargs grep searchterm

Or:

sudo find path -name regex | xargs grep -wni

What do you think if we restrict to maxdepth=3D1 for Darwin? Otherwise =
it=20
will take ages before we can have something functional if ever.

Mich=E8le
<http://micmacfr.homeunix.org>