Dolphin doesn't trim extra slashes in the names of the directories I create visually. Til I know, the char slash "/" ist'n allowed to naming files or directories on unix systems. Reproducible: Always Steps to Reproduce: 1. In a empty area on screen, mouse right button, create new, directory (here it's translated, so I don't know if the original string is folder or directory) 2. in the dialog, type my new directory//// 3. click in ok Actual Results: it's created a new directory with the name "my new directory⁄⁄⁄" Expected Results: the creation of a directory named "my new directory", without extra slashes
Ohh nice one! Frank, What's the intended case here? If one types: "folder_name///" Should that be interpreted as: "folder_name" And what if one types: "folder////some_other_folder" Should that be interpreted as: "folder" - "some_other_folder" (so that you can create recursive folders) Your input would be nice :)
This replacement is actually made by KIO and is intentional, see http://permalink.gmane.org/gmane.comp.kde.devel.kfm/13363
The intention is a bug. A very serious one. If KIO is so broken, the applications need to protect us from this. If I tell it to make a / and it makes an arbitary ⁄
Right, re-assigning to KIO to let them decide.
Doesn't happen for directories, but still happens for files. The inconsistency is not good.
For directory names it looks like KNewFileMenu if you type a/b/c, would create a, then b and c as sub-dirs of a. The / is converted into a fraction slash because there is no way to have / as part of a file or dir names, because it's the dir path delimiter/separator: https://commits.kde.org/kdelibs/53659edb4b1841474a23952746e68a1222756fec Personally, I think / should be disallowed as part of file/dir names altogether... it has some potential side-effects, see bug 400469.
I can't reproduce this bug with today's directory creation dialog. It shows the structure that is about to be created, pretty precisely, and no fraction slash is involved. Arguably it could trim trailing slashes to avoid showing a wrong structure like my new directory / / / But that's a minor bug and not exactly the one reported here. This bug is actually fixed.