Bug 398830 - Suggest new name inserts spaces
Summary: Suggest new name inserts spaces
Status: RESOLVED DUPLICATE of bug 317320
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: git master
Platform: Other Linux
: NOR minor
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-19 09:26 UTC by davidblunkett
Modified: 2018-09-24 19:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description davidblunkett 2018-09-19 09:26:54 UTC 
If you save an attachment the suggest new name feature adds spaces and this is a PITA, please change to underscores
Comment 1 Nate Graham 2018-09-19 22:10:44 UTC 
Why are spaces a PITA?
Comment 2 Nate Graham 2018-09-19 22:12:07 UTC 
Haha, you already filed this years ago! I thought it seemed familiar.

Still intentional, I'm afraid.

*** This bug has been marked as a duplicate of bug 317320 ***
Comment 3 davidblunkett 2018-09-24 07:17:02 UTC 
Spaces are a PITA because they are the standard shell delimiter between tokens (as I am sure you know) which makes scripting and using the filenames from shells a PITA.

Let me ask the counter question: what's wrong with _ ?
Comment 4 Nate Graham 2018-09-24 19:33:06 UTC 
Sorry, but the kind of expert who uses the shell a lot should be able to deal with spaces. I'm in a terminal all day and spaces are not a PITA. Just escape them or quote your strings.

What's wrong with using underscores instead of spaces is that it would help people who do their file management from a terminal, but would annoy regular people who use spaces between words, and would subtly signal to them that KDE Software is made primarily for sysadmins and programmers, not for them.

We're not going to change this, sorry. Since you are a technical expert, you are more than welcome to patch the code and use underscores yourself. Christoph Feck even showed you the exact line of code you need to change in https://bugs.kde.org/show_bug.cgi?id=317320#c8.