Re: [PATCH] Need gnatsd command to retrieve multienum separators

[Nick Bower]

>     NB> Just a thought - how about addressing the problem of making the
>     NB> existing ':' field separators work first? :) We can't have
>     NB> spaces in either the category or responsible "keys", but I know
>     NB> you guys are aware of this
> 
> Finally I am. :-)  There is the following comment in the source:
> 
>    /* XXX ??? !!! Enum fields are terminated after the
>       first space character.  Why?  */
> 
> I can't answer the comment question, so I'm removing the space
> termination code now.

ok - i've tested this by placing a in a reponsible enumeration like
"Intranet Support", but it's still not working 100%.  from gnatsweb:

Unparseable reply from gnatsd Intranet... User unknown 

Unparseable reply from gnatsd /usr/local/share/gnats/dead.letter...
Saved message in /usr/local/share/gnats/dead.letter 

I'd give more debugging info from gnatsweb, but there's a problem here
too.  Turning on gnatsweb debugging flags gives the following internal
server error:

[Mon Oct 29 13:35:48 2001] gnatsweb.pl: ; user=nick, db=default;
stacktrace: In: main::get_reply <= main::client_cmd <= main::unlockpr <=
main::submitedit <= main::main at
/brains99/Data/httpd/cgi-bin/gnatsweb.pl line 414, <SOCK> line 306.

by the way, there seems to be no problem putting a space in a category
enumeration - this now works and it's just the responsible field that's
causing continued problems.

cheers, nick