Exceptions for Workspace/Tags

amix · Post by **amix** » Fri Aug 24, 2007 1:47 pm

Hi!

I store several complex Javascript/HTML files (different TiddlyWiki incarnations) in my workspace. Rebuilding the workspace lasts pver two minutes each time something gets added to the workspace. Is there a way to exclude certain files from this process ?

Post by **jussij** » Mon Sep 17, 2007 2:22 am

Is there a way to exclude certain files from this process.

One option would be to use the Workspace Options menu and in the Tags section select the Disable the automatic updating.. option.

This will turn of the automatic builds but the tags can still be updated manually via the Tags, Rebuild and Tags, Make menus.

A second option is to add all the excluded files to their own project and once again disable the make for that project.

Finally it should also be possible to download the ctags source and create a modified ctags.exe (xtags.exe) that excludes files of a given extension.

Cheers Jussi

amix · Post by **amix** » Mon Sep 17, 2007 11:32 am

Okay. My current project's startup-time lasts four mintues. It may be, that it was me who misunderstood the right use of the projects. I store several projects in different folders and have them all in the same Zeus Workspace, since that seemed the most logical to me:

Workspace (of related projects)
--project01
----docs
----source
----buidl
----etc.
--project02
----docs
----source
----buidl
----etc.

I think, that the tags get built on startup of a project anyway, since, if I remember correctly, I already switched off the automatic-build.

Post by **jussij** » Mon Sep 17, 2007 1:02 pm

How many files are contained in the workspace and approcimately how many lines of code do these files represent

Also if you use the Tags rebuild menu, how long does a full tags rebuild take

I would have expected a Zeus workspace of some 100 or so files would only take a few seconds tol load

Cheers Jussi

amix · Post by **amix** » Mon Sep 17, 2007 5:43 pm

202 files, approx. 30 of them HTML, the others mostly Javascript and a very few simple text-files. They are within 9 projects and maybe 10 folders.

I measured the startup of the project (I removed the project from Zeus startup (closed it before closing Zeus), so I reloaded it manually. It took 3:28 minutes.

Manual rebuild took 3:01 minutes.

Oh...as I relized now, I switched off the built-in tagger, but only for the default-project. Now, that I re-enabled it manual rebuild seems to happen within less than a second.

Post by **jussij** » Mon Sep 17, 2007 11:27 pm

Oh...as I relized now, I switched off the built-in tagger, but only for the default-project.

So the slow loading was caused by the tags make which is done when the workspace is loaded.

But I am not sure why the make is taking so long to run on your workspace

In comparison the Zeus workspace is 6 project spread over some 370 files and it opens in less than 2 seconds. The majority of this time is spent running a tags make on the workspace.

For example a Zeus workspace tags make will complete in about a second while a full tags rebuild takes about 30 seconds.

I would have expected a workspace of this size to open in only a few seconds

Cheers Jussi

amix · Post by **amix** » Tue Sep 18, 2007 8:48 pm

jussij wrote:So the slow loading was caused by the tags make which is done when the workspace is loaded.

But I am not sure why the make is taking so long to run on your workspace

Well, when I switched on the internal process, then it became as speedy as you described. Could it be, that the external ctags.exe takes so long but not the internal use of the ctags library ?

Also, please be aware, that this is mainly Javascript and HTML files, so it may well be, that the support for these off-road languages is sub-optimal. I would assume, that development is being focussed on C,C++ and maybe Java.
(Nobody cares for us scripting guys, sniff

)

Post by **jussij** » Tue Sep 18, 2007 11:20 pm

Well, when I switched on the internal process, then it became as speedy as you described.

Ok, that does explain the reason for the slow updates. Excellent

Could it be, that the external ctags.exe takes so long but not the internal use of the ctags library?

The external mode represents the original Zeus ctags support while the internal mode is a more recent addition. But both modes still use the ctags.exe (xtags.exe) to generate the tags.

The difference is in external mode Zeus leaves the build process up to ctags.exe which does a full re-build of all files, while for internal mode Zeus manages the build process and it will only build files that have changed

I will add a warning message box to tell the user the external make is slower than the internal make

Also, please be aware, that this is mainly Javascript and HTML files, so it may well be, that the support for these off-road languages is sub-optimal.

I have noticed that ctags does favour certain languages more than others

Cheers Jussi