Bug#689842: shelldap: RDNs with spaces are handled differently by different commands

2012-10-10 Thread Salvatore Bonaccorso
Hi Dominik On Sun, Oct 07, 2012 at 09:09:48PM +0200, Dominik George wrote: > > The manpage should at least document that if there are RDNs with > > spaces, then they need to be quoted. I do not see an easy way (right > > now) on how the code could be changed to parse the arguments to cat > > and r

Bug#689842: shelldap: RDNs with spaces are handled differently by different commands

2012-10-07 Thread Dominik George
Hi, > The manpage should at least document that if there are RDNs with > spaces, then they need to be quoted. I do not see an easy way (right > now) on how the code could be changed to parse the arguments to cat > and rm in better way. then just invert that. Make all commands that do not take a s

Bug#689842: shelldap: RDNs with spaces are handled differently by different commands

2012-10-07 Thread Salvatore Bonaccorso
Control: tags -1 + upstream confirmed Control: forwarded -1 http://projects.martini.nu/shelldap/ticket/10 Hi Dominik On Sat, Oct 06, 2012 at 11:53:58PM +0200, Dominik George wrote: > Package: shelldap > Version: 0.5-2 > Severity: normal > > Having RDNs like "cn=Foo Bar" causes unexpected behavio

Bug#689842: shelldap: RDNs with spaces are handled differently by different commands

2012-10-06 Thread Dominik George
Package: shelldap Version: 0.5-2 Severity: normal Having RDNs like "cn=Foo Bar" causes unexpected behaviour for some commands. - edit cn=Foo Bar- works - cat cn=Foo Bar - expects "" - cd cn=Foo Bar - works - rm cn=Foo Bar - expects "" All commands should expect "" for RDNs with