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