What steps will reproduce the problem?
1. $./httpsqs -x ~/
2. the httpsqs_settings_dataname=/home/foo//httpsqs.db
What is the expected output? What do you see instead?
httpsqs_settings_dataname=/home/foo/httpsqs.db
同时判断输入目录合法性
What version of the product are you using? On what operating system?
1.7
Original issue reported on code.google.com by
[email protected]on 1 Jul 2012 at 11:07Attachments: