bug-global
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: suggestions for global


From: Shigio Yamaguchi
Subject: Re: suggestions for global
Date: Fri, 15 Feb 2002 22:00:59 +0900

Hello,
> our company uses global for a quite big project (analySIS about 150 MB
> source code). Most important for us is the possibility to browse the =

It's great!

> 1. Most people don't like the differentiation between capital and small
> letters for file names.

If so, why do you use both of capital and small letters?

> 2. Some people would be happy if they could use the simple wild cards * and
> ? instead of the complex regular expression syntax.

I agree. I'll add this into TODO list.

> 3. I want to integrate a search engine like htdig to be able to search even
> for comments etc. So I need a simple possibility to integrate the search
> front end into the global front end. My idea is that it should be possible
> to define html-templates (maybe XML?) for the frames. Then everybody is able
> to change the design, to add functionality or simply additional links in the
> company's intranet. Different themes of html-templates could be integrated
> in the global package.

Is it so important to integrate some facilities into one screen?
I think it is more flexible to load another browser.

Isn't it better to integrate search engine into global(1) rather than
into hypertext.  Is htdig applicable for local files?

> 4. gtags works only on one directory. The result is that header files that
> are located elsewhere (like /usr/include/stdio.h) are not indexed. So it is
> impossible to search for "printf" for example.  A solution would be to add
> an include path option to gtags.

Gtags(1) works only on one directory but global(1) locates a number of tag
files using GTAGSLIBPATH environment variable. Is it inadequate?

> 5. It would be great to find a solution for pathnames containing spaces (I
> know that this seems not to be possible).

I think it is a bad style to contain spaces in a pathname because many
UNIX tools assume space as a sepalator. But I don't disagree such facility.
If you can implement such facility without problem then I'll include your
patch into core GLOBAL.
By the way, why do you want to use spaces in pathnames?
--
Shigio Yamaguchi - Tama Communications Corporation




reply via email to

[Prev in Thread] Current Thread [Next in Thread]