cssed-devel — cssed development discussion

Re: [cssed-devel] Test for find_in_files plugin

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

Le 10 sept. 2004, =E0 12:25, Iago Rubio a =E9crit :

> On Fri, 2004-09-10 at 04:34, Mich=E8le Garoche wrote:
>>> Other than that, it seems to work.
>> Sorry, it crashes when searching on $HOME. xargs: unterminated quote,
>> then bus error.
>
> I'm working on it.
>
> I will send changes to cvs soon.
>
> If it gets failing this way, I will rewrite it without threads using=20=

> the
> g_spaw* GLib functions, that are more portable.
This one is an old message, it works, but it only prints one line.

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

Re: [cssed-devel] Test for find_in_files plugin

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

On Fri, 2004-09-10 at 04:34, Mich=C3=A8le Garoche wrote:
> > Other than that, it seems to work.
> Sorry, it crashes when searching on $HOME. xargs: unterminated quote,=20
> then bus error.

I'm working on it.=20

I will send changes to cvs soon.

If it gets failing this way, I will rewrite it without threads using the
g_spaw* GLib functions, that are more portable.
--=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

Re: [cssed-devel] Plugin problems in BSD and MacOsX

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

On Fri, 2004-09-10 at 18:08, Mich=C3=A8le Garoche wrote:
> Le 10 sept. 2004, =C3=A0 17:56, Iago Rubio a =C3=A9crit :
>=20
> > The find in files plugin is being fixed and I expect a working update
> > tomorrow.
> I'm waiting for it :-)
>=20
>  From my investigation, it works with the getline you have commented=20
> out, then if you use:
>=20
> find /Users/toto -maxdepth 1 type -f | xargs grep -n "foo"
>=20
> it should work (at least it works on the command line)
>=20
> The problem is a permission problem and a type problem and a depth=20
> problem.
> 1 - You could not search at depth 0
> 2 - You could not search files that are not regular files (I mean=20
> printer drivers, symbolic links, directories) with this syntax.

Oh! Great help, lots of thanks.=20

I was fiddling in the getline function and was unable to fix it.

> See if it works on BSD with this syntax (maxdepth >=3D1 and obligatory),=20
> type -f (silently added).

Will do it right now.

Thanks again.
--=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

[cssed-devel] Re: Plugin problems in BSD and MacOsX

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

On Fri, 2004-09-10 at 17:56, Iago Rubio wrote:
> I'm even thinking about two plugins one for ctags and other for
> exuberant ctags.

Ok, I think it will be the approach.

I installed exuberant ctags on BSD and the plugin worked fine with a
small patch to rename ctags to exctags in BSD systems, to avoid clashes
between both programs.

I was wondering how it works in OsX, as it does not changes the package
name but uses something called "update-alternatives".

Michelle any idea ??
http://fink.sourceforge.net/pdb/package.php/exuberant-ctags

It's maintained by pogma, can you ask him how we can know the ctags
binary is exuberant ctags or not ?

The ctags plugin is to come, the current one will be only for exuberant
ctags and will be - surely - renamed.

The idea on this plugin, was to use the exuberant ctags support for web
languages as PHP, HTML and much others (as Java, Javascript, Perl, sh,
python, Makefiles ... ) in cssed.

ITOH I'm writing support for CSS tags on exuberant ctags, but can not
bind it to ctags.

Using just the ctags program we can not search anything but C source
code, that's not really useful for cssed.

Am I wrong with this ?

Does the ctags program find any other tag than C tags ?=20

I've got in mind it can search throught Lisp, Fortran,Pascal, C, lex and
yacc sources.=20

Nothing apropiated to use in cssed.
--=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

Re: [cssed-devel] Plugin problems in BSD and MacOsX

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

Le 10 sept. 2004, =E0 17:56, Iago Rubio a =E9crit :

> The tags plugin must include two interfaces one por ctags (BSD, OsX)=20=

> and
> other for exuberant ctags (the one working now).
No, the other way around, on Mac OS X, this is exuberant ctags, but the=20=

name in configure in ctags, then  configure does not find it.

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

Re: [cssed-devel] Plugin problems in BSD and MacOsX

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

Le 10 sept. 2004, =E0 17:56, Iago Rubio a =E9crit :

> The find in files plugin is being fixed and I expect a working update
> tomorrow.
I'm waiting for it :-)

 =46rom my investigation, it works with the getline you have commented=20=

out, then if you use:

find /Users/toto -maxdepth 1 type -f | xargs grep -n "foo"

it should work (at least it works on the command line)

The problem is a permission problem and a type problem and a depth=20
problem.
1 - You could not search at depth 0
2 - You could not search files that are not regular files (I mean=20
printer drivers, symbolic links, directories) with this syntax.

See if it works on BSD with this syntax (maxdepth >=3D1 and obligatory),=20=

type -f (silently added).

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

[cssed-devel] Plugin problems in BSD and MacOsX

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

After Michelle's tests on MacOsX, I tested the plugins on FreeBSD and
the same problems are present in both systems.

The plugins: find in files plugin, and tag plugin does not works on BSD
and MacOsX.

I'm working on them but will require some work.

The find in files plugin is being fixed and I expect a working update
tomorrow.

If I don't get it tomorrow, I will completly rewrite it using glib
functions.

The tags plugin must include two interfaces one por ctags (BSD, OsX) and
other for exuberant ctags (the one working now).

There will be a compile option to choose one or other, and will fallback
automaticaly for the default tags program ( exuberant ctags on Linux,
ctags on *BSD and OsX ) if no option is passed.

Other minor fixes are to come in both interfaces.

I'm even thinking about two plugins one for ctags and other for
exuberant ctags.
--=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

Re: [cssed-devel] Test for find_in_files plugin

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

On Fri, 2004-09-10 at 01:59, Mich=C3=A8le Garoche wrote:
> First, I've changed the plugin name to cssed-findinfiles-plugin to be=20
> consistent with other plugins. Hence changes in configure.in,=20
> src/Makefile.am.

ok.

> Second it does not compile on Mac OS X, since it has a _getline symbol=20
> undefined. This is a known bug, this symbol is not exported.=20

The same apply in BSD, as it have no getline.

> Could you=20
> find another way to do it?

Sure, I will change it if fails on OsX.
--=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

Re: [cssed-devel] Change strings in filebrowser-plugin sources

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

On Thu, 2004-09-09 at 22:56, Mich=C3=A8le Garoche wrote:
> I've changed the strings in various files in filebrowser-plugin source=20
> files so that the first letter gets capitalized in UI. As well as=20
> updated the pot file and changed the po files (both es and fr). All=20
> committed.
>=20
> Here's the diff

________________________________________________________________________
> The plugin works fine for me.

Great, thanks :)
--=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

Re: [cssed-devel] Tests on cssed cvs - new highlightings

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

On Thu, 2004-09-09 at 18:16, Mich=C3=A8le Garoche wrote:
> There are some minor glitches when highlighting html files, when=20
> multiple lines are wrapped, that is not always the first one which is=20
> shown but the line before the last one.

Could you please elaborate a little on this ?? :)

> For php files, the comments do not seem to be recognized correctly.

PHP comments are // and /* */ (c style comments). The html comment is
not valid into a PHP block.

Are those comments bad highlighted in your system ?

For		It should highlight as comment
---		------------------------------
PHP		//	/* */
javascript	//
pythonscript	#
vbscript	'
ASP		//	/* */

> Other types of files seems to be highlighted correctly (as far as I can=20
> judge).

Sure they will be small glitches to correct in the future, but the
overall highlighting must work (or we'll take out the highlighting and
fix it).

The tokenizers used for the new highlightings are used by various well
known projects as Anjuta and Komodo and are roughly tested.=20

The tokenizer for CSS is only used by cssed, but I think It works fine
right now.

What I'm checking are the color schemes as only the CSS one is
configurable.

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

Re: [cssed-devel] Test for find_in_files plugin

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

Le 10 sept. 2004, =E0 4:21, Mich=E8le Garoche a =E9crit :

> Other than that, it seems to work.
Sorry, it crashes when searching on $HOME. xargs: unterminated quote,=20
then bus error.

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

Re: [cssed-devel] Test for find_in_files plugin

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

What is it supposed to do? I only get one line when I search for a=20
term. I would have thought I got as many lines as the term occurs in=20
the files found recursively (at the given depth) in the given base=20
directory.

Maybe it is related to the fact I've changed getline definition?

Other than that, it seems to work.

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

Re: [cssed-devel] Test for find_in_files plugin

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

Le 10 sept. 2004, =E0 1:59, Mich=E8le Garoche a =E9crit :

> Second it does not compile on Mac OS X, since it has a _getline symbol=20=

> undefined. This is a known bug, this symbol is not exported. Could you=20=

> find another way to do it?
I've disabled the comments around #ifdef BSD and the corresponding=20
#endif in callback.c (i.e. I've removed the lines) and it loads. So,=20
probably a #ifdef DARWIN would be appropriated here.

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

[cssed-devel] Test for find_in_files plugin

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

First, I've changed the plugin name to cssed-findinfiles-plugin to be=20
consistent with other plugins. Hence changes in configure.in,=20
src/Makefile.am.

Second it does not compile on Mac OS X, since it has a _getline symbol=20=

undefined. This is a known bug, this symbol is not exported. Could you=20=

find another way to do it?

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

[cssed-devel] Change strings in filebrowser-plugin sources

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

I've changed the strings in various files in filebrowser-plugin source 
files so that the first letter gets capitalized in UI. As well as 
updated the pot file and changed the po files (both es and fr). All 
committed.

Here's the diff

[cssed-devel] Correction of fr.po file

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

Silly error, sorry.

Re: [cssed-devel] Proposed patch for main.c

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

Le 9 sept. 2004, =E0 18:45, Iago Rubio a =E9crit :

> On Thu, 2004-09-09 at 17:44, Mich=E8le Garoche wrote:
>> As I don't know if it is right (though it works on Mac), I just make =
a
>> proposal to avoid compile failing when no ipc queue is defined. Here=20=

>> it
>> is (not committed, just applied locally for make further tests
>> possible):
> Sorry, my fault.
> Those variables must be declared out of the #ifdef block.
> Fixed in cvs, patch attached.
Ok, thanks Iago.

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

Re: [cssed-devel] Proposed patch for main.c

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

On Thu, 2004-09-09 at 17:44, Michèle Garoche wrote:
> As I don't know if it is right (though it works on Mac), I just make a 
> proposal to avoid compile failing when no ipc queue is defined. Here it 
> is (not committed, just applied locally for make further tests 
> possible):

Sorry, my fault.

Those variables must be declared out of the #ifdef block.

Fixed in cvs, patch attached.
-- 
Iago Rubio   
- Home page    * http://www.iagorubio.com 
- Last project * http://cssed.sourceforge.net         
- GPG Keyserv  * pgp.rediris.es id=0x909BD4DD

[cssed-devel] Tests on cssed cvs - new highlightings

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

There are some minor glitches when highlighting html files, when=20
multiple lines are wrapped, that is not always the first one which is=20
shown but the line before the last one.

For php files, the comments do not seem to be recognized correctly.

Other types of files seems to be highlighted correctly (as far as I can=20=

judge).

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

[cssed-devel] Proposed patch for main.c

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

As I don't know if it is right (though it works on Mac), I just make a 
proposal to avoid compile failing when no ipc queue is defined. Here it 
is (not committed, just applied locally for make further tests 
possible):

[cssed-devel] Corrected interface.c

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

Sorry for the typo, commited.

[cssed-devel] Update of include/header files

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

I've corrected misspelling and committed the changes in various 
include/header files. I've also added a ChangeLog to track the changes.

Here's the diff

Re: [cssed-devel] Plugins in CVS

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

On Fri, 2004-09-03 at 21:54, Mich=C3=A8le Garoche wrote:
> Le 3 sept. 2004, =C3=A0 21:42, Iago Rubio a =C3=A9crit :
>=20
> > I've uploaded some modules to CVS,

> I've not checked against cvs, but built them from the location you gave=20
> before.
>=20
> filebrowser seems to work.

Great.

> tags works more or less, there is problem when you want open a tag=20
> file, the file could not be found, should be related to the fact you=20
> have or not the filebrowser-plugin loaded too, or that the file's name=20
> needs a conversion before being handle by the system or the program.=20

Will check it. The tag-plugin created files defaults for "ptags" to
avoid classes with "tags" created by ctags, and TAGS created by emacs.

It should not give problems with the open file function.

It also fails before to create a tag file using the plugin's button ??

It should open it automaticaly (In fact the file is opened each time is
read, it takes the file's name from the grayed entry in the plugin's
ui).

> By=20
> the way, if you use exuberant ctags, instead of ctags, it would be just=20
> fine. Otherwise it works with a patch. But I cannot test it in depth,=20
> since I never used ctags, it's kind of new land for me.

May be the problem is a tag file created without the full path to the
tags into, so when you click in a tag, it tries to open it from the
current dir, not from the directory where the tag file was created.

Try "ctags -R -V --excmd=3Dnumber -f ptags `pwd`" and open the file
created - if any - in cssed's tag plugin (or cssed itself).

The tag should look like:

"browser_get_agent      /var/www/html_ext/library.php   110;"   f

... with the full path, not:

"browser_get_agent      library.php   110;"   f

In the tag-plugin window the full path must be visible in the "file"
column.

It can be solved in future releases, checking if the path is not
absolute to add to the file's name the tag file base directory.

Tags are indeed really usefull and I'm trying to add CSS suport to
ctags, so it's planned that it will also scan CSS file looking for tags.

I've got a simple config to drive ctags to recognize CSS file, but it's
really bad and only works with perfectly formated CSS file, in the form

a{
	color:red;
}

As example "a{color:red;}" will not work and even worst:

a{
color:red;
}

So it's unusable right now.

> I've not tested quicksearch-plugin but it builds.

It's somewhat stupid. Don't take it really into account. It's just an
add that likes me, but I know it have no use for most people, as the
find dialogs are much better.

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

[cssed-devel] Plugins in CVS

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

I've uploaded some modules to CVS,

* filebrowser-plugin : provides a file browser panel.

* findinfiles-plugin : provides support for find in various files (
needs find, grep and xargs ).

* tags-plugin : support for reading/creating tag files ( produced by
ctags --excmd=3Dnumber ... ).

* quicksearch-plugin : this is stupid but I like it, provided a small
search entry in the toolbar.


Only the filebrowser-plugin module is completly cleaned up, the others
will need some work.

Michelle, you should have write access to all those modules. Test it if
you find some time.

For others who want to test them:

cvs -d:pserver:ano...@cv...:/cvsroot/cssed login =20
cvs -z3 -d:pserver:ano...@cv...:/cvsroot/cssed co
modulename

Being modulename one of:

        filebrowser-plugin
        findinfiles-plugin
        tags-plugin
        quicksearch-plugin=20
--=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

[cssed-devel] New doc.

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

I've just checkout(ed) the documentation and it's a great job Michelle,
thanks.

I can't build the doc some times ago because the lack of some scripts,
but now builds cleanly in my system and looks really good.

Errr, may be it's time to update it to current version, isn't it ?
--=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