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

[Iago R. <iag...@hi...>]

On Tue, 2004-09-14 at 17:11, Mich=C3=A8le Garoche wrote:
> Le 14 sept. 2004, =C3=A0 14:50, Iago Rubio a =C3=A9crit :
[snip]
> > 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.

It's a bug.

> >> 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.

Mostly a task for the find dialog, isn't it ?

> > If so I must add another menu item to the pop menu.
[snip]
> > 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.

Yes, we could add a pop menu entry for the quickserch plugin.

> >>> 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.

Usually find separate file names with a carriage return, with -print0 it
changes the carriage return by a null character '\0'.

If it cxhanges find behaviour in any other way, it's a bug in find.

I must take a closer look at this.=20

> >> 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
>=20
> > 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:
>=20
> find path -name regex | xargs grep searchterm
>=20
> Or:
>=20
> sudo find path -name regex | xargs grep -wni
>=20
> 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.

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.

--=20
Iago Rubio  =20
- Home page    * http://www.iagorubio.com=20
- Last project * http://cssed.sourceforge.net        =20
- GPG Keyserv  * pgp.rediris.es id=3D0x909BD4DD