| Summary: | Dolphin allows you to safely place slashes file names, but for folder names, doing this creates a folder hierarchy | ||
|---|---|---|---|
| Product: | [Applications] dolphin | Reporter: | Laptander <dev-laptander> |
| Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | minor | CC: | amak79, nate, olaf.the.lost.viking |
| Priority: | NOR | ||
| Version: | 15.12.1 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
Are you sure it is adding a "/" (slash) and not a "⁄" (fraction)? I just tried it out within a plasma workspace and it is trying to create fractions. When my filename ends with a number, it puts it "on top" of a fraction... (Not saying this is a good idea - but a slash symbol in the filename shouldn't even be possible.) Yes, I suspected that it is not actually slash, but another symbol due to it was looking a bit different. So this is not a bug? In my case when I name file or folder ending with fraction with digit under kde, it do not place it on top of it. I created this report because it confused me. As I remember, dolphin was giving such warning when you tryed to use slash in file name. But now it just changes slash to math division slash. Ok, maybe it is a smart solution to not distarb user. But why when you are creating a directory for example "a/b" than it creates "a" and inside of it it creates "b". If in one case it changes slash to fraction, why not in another case? I recently encountered this issue. I couldn't understand how Dolphin was creating a directory with a forward slash in the name. I only realized it wasn't a forward slash after the directory name string returned 'utf-8' for the encoding. I agree with comment 1. Dolphin should warn the user, not convert a forward slash to a fraction slash. They are different symbols, even though they look almost identical. Using a visually similar character is actually a usability feature: we try to do what the user intended (even if it's not via the same approach) rather than display a nasty error that then tries to explain some technical gibberish about unsupported characters. If there's any issue here, it's the inconsistency of having slashes in folder names create a hierarchy rather than using the same behavior as with slashes in file names. (In reply to Nate Graham from comment #4) > If there's any issue here, it's the inconsistency of having slashes in > folder names create a hierarchy rather than using the same behavior as with > slashes in file names. I do agree with you on this point. The behavior should be the same for files and directories, whether slashes are allowed or not. *** This bug has been marked as a duplicate of bug 251830 *** |
If user is using cinnamon and decided to rename or create file of directory in dolphin and he/she place a forward slash ('/') symbol in its name, then dolphin would just create/rename file with such name. Reproducible: Always Expected Results: It should warn user about "slash is not permitted in file names" as it does when user is using kde.