Re: [LDAPsh-devel] ldapsh feature requests

[James D. <j-d...@us...>]

Hi,

In message <200...@ka...>
on Mon, Feb 02, 2004 at 05:29:02PM +0100, Sebastien Gross wrote:
>         - when a C-t is done, the command line should be cleared the
>           begin of the command redisplayed

Thanks; fixed in CVS.

> I was wondering if some feature/enhencement could be included:
>         - vi with option to fetch and add MUST/MAY fields in the edited
>           file

I added MUST/MAY for /new/ entries, though it is difficult to add these
when editing /existing/ entries. The reason is that the output file is
created by a function that is part of the Net::LDAP::LDIF Perl module.
We would have to filter the output in order to intersperse MUST and MAY
annotations. On the up side, this might also give us the opportunity to
sort attribute names alphabetically. Do you think it would be better to
put unused MAY attributes at the bottom of the LDIF file or better to
put them in their alphabetical location?

>         - when I create a new user I got the following message:
> 
> new cn=zero top person inetOrgPerson organizationalPerson posixAccount
> LDAP Error adding entry 'cn=zero, ou=users,dc=chezwam,dc=org'. Code:21.
> Message:description: value #0 invalid per syntax
> LDIF stored in LDAPShell_vi_PnfAMwE9zZ.ldif
> 
>           this should be because some fieds are left empty (or with only
>           a space).

I'm not sure if Net::LDAP gives us the facility to check each attribute
value for its correct syntax. And if a blank line is /valid/ syntax, how
do we know whether we should remove that line? I don't know enough about
LDIF/LDAP to decide on the correct behaviour. Perhaps we should add a
warning comment at the top of each new entry? As a consolation prize,
perhaps we could add a -p ("prune") option to the create/new commands so
that users can opt to have empty lines removed.