Bug 383376

Summary: Warn when user enters leading or trailing spaces into file or folder name
Product: [Applications] dolphin Reporter: Gregor Mi <codestruct>
Component: view-engine: generalAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: elvis.angelaccio, jesiphone2020, nate
Priority: NOR    
Version First Reported In: 17.04.3   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Gregor Mi 2017-08-10 18:34:16 UTC 
I observed that it can cause confusion when files or folders contain leading or trailing whitespace characters.

Suggestion:

Show a warning when a user is about to create a file or folder with leading or trailing whitespace. The warning could contains three options:
1) Strip spaces automatically
2) Continue anyway
3) Go back to edit the name again
Comment 1 Nate Graham 2017-08-10 19:58:07 UTC 
I worry that the sorts of users who don't notice unwanted leading or trailing spaces are highly likely to blindly click through warning/confirmation dialog boxes.
Comment 2 Gregor Mi 2017-08-11 05:56:19 UTC 
This is one reason to make the "Strip spaces automatically" option the default one.
Comment 3 Elvis Angelaccio 2017-08-12 07:58:45 UTC 
How about making the leading/trailing spaces visible/recognizable, like klipper does?
Comment 4 Gregor Mi 2017-08-13 10:48:56 UTC 
> How about making the leading/trailing spaces visible/recognizable, like klipper does?

Ah, I didn't know that klipper does this (for leading/trailing characters I see space, tab and newline symbols with blue font color). Sounds like a possible solution.
Comment 5 Jonathan E. Snow 2020-05-19 17:11:05 UTC 
I get bitten by this all the time. Dolphin happily creates folders with trailing spaces, but then *other* applications can't write to them and the error messages generated are non-obvious. 

Dolphin should strip trailing spaces by default. Or it should be settable.
Comment 6 Nate Graham 2020-05-19 17:15:56 UTC 
Ah, I just fixed this, in a form.

*** This bug has been marked as a duplicate of bug 421075 ***