When dolphin suggests a new name it appends " X" before the extension where X is a number. The problem is it also inserts a space " " before the number. Since dolphin is used on a linux filesystem is should be expected that the filename will be used from a shell and this space requires escapes or quotes to use. It would be far better is dolphin used an underscore "_" instead of a space " " when suggesting a new name. At the very least this should be user definable. Reproducible: Always Steps to Reproduce: 1. Copy a file to a directory with the same name as an existing file 2. Let dolphin suggest a new name et voila a space appears 3. Actual Results: You get spaces in filenames Expected Results: At more suitable space character should be used (the underscore "_")
Thanks for the report, but I don't see the bug here. It's perfectly possible to use file names with spaces from a shell, the tab auto completion even adds the escaped space for you.
I disagree - using a space is a poor choice for all sorts of a reason, and underscore has none of these disadvantages. As for completion - it depends on which shell and what context you are using and it is a PITA for scripts. It should be a user definable option at the very least. I cannot see any argument for using a " " over a "_" and lots the other way around.
I think we should append the number without a prefix.
Sorry, but avoiding spaces at all costs is not a reasonable behavior. Real people use spaces in their file names, and real tools handle them gracefully. Shells and CLI tools that can't handles that aren't worth the bits they're printed on, and you should file bugs against them (or even better, submit patches) to fix that.
Real people and real tools use "_" and 50 years of computing practice uses " " as a token separator which this (annoyingly) breaks. There hasn't been an answer given here as to why not "_" or something else that behaves nicely with the system you're building on!
The people who use underscores in their file names are programmers and command-line power users. We aren't optimizing the system for them; we're optimizing it for people with more normal levels of computer skills, who by and large use spaces in their file names.
Perhaps you should be developing for Windows?
That's not a helpful comment. I suggest to simply replace the Space in https://cgit.kde.org/kio.git/tree/src/core/global.cpp#n397 and recompile KIO.
> That's not a helpful comment. Do you mean Nate's comment above?
No.
Ok - well I didn't think Nate's comment was useful because I read this as "we're just catering for the computer illiterate". I've fail to see why underscores inconvenience novices!
*** Bug 398830 has been marked as a duplicate of this bug. ***
*** Bug 404559 has been marked as a duplicate of this bug. ***