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

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

Le 15 sept. 2004, à 10:04, Iago Rubio a écrit :

> On Tue, 2004-09-14 at 22:25, Michèle Garoche wrote:
>> Le 14 sept. 2004, à 22:17, Iago Rubio a écrit :
>>> On Tue, 2004-09-14 at 17:11, Michèle Garoche wrote:
>>>> Le 14 sept. 2004, à 14:50, Iago Rubio a écrit :
>>>>>> 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
>>>>> 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
>>>> the search term given in the search term entry in the bottom panel.
>>> Mostly a task for the find dialog, isn't it ?
>> Yes, exactly.
> This dialog must be updated. Right now it only searches from caret
> position to end of document. The bits to search backwards are in place
> so I must update it.
It works for me backwards and upwards.

>>>> What do you think if we restrict to maxdepth=1 for Darwin? Otherwise
>>>> it
>>>> will take ages before we can have something functional if ever.
>>> We can easily do it by hidding all the depth related widgets, and a
>>> couple of #ifdef.
>>> May be we could limit maxdepth meanwhile we don't find a better
>>> solution, and go for the release,
>>> The we could have time to further investigate those problems.
>> Yes, I think so, but don't impede other systems to use the most of it,
>> just restrict it on systems where there are problems.
> And as find is bogus there, what about egrep.
> We can avoid maxdepth and set recursive or not.
> Non recursive:
> egrep -in term
> Recursive:
> egrep -irn term
> Does it works in your system ?
It does not work at all on my system, so I've reintroduced the first 
string for search, it is not perfect, but that's the most valid one at 
the moment.

Here's the diff: