https://bugs.kde.org/show_bug.cgi?id=421075
Larry Dewey <larry.j.de...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO |---
--- Comment #2 from Larry Dewey <larry.j.de...@gmail.com> ---
(In reply to Nate Graham from comment #1)
> Can you explain why you think this should happen? What problem is it causing
> you? Bug reports that just describe a problem are usually more helpful than
> ones that propose a solution without explaining the problem.
Can you explain why you think this should happen?
There are a number of reasons that I feel it should happen:
1. Consistency with other file managers.
- Nautilus, Thunar, Nemo, etc all prevent you from entering
a name with a trailing or leading white space.
2. Ease of use.
- In most instances users do not mean to place a leading
or trailing white space when naming their directories or
file names.
- Saving files to samba, nfs, or sshfs file shares fail to
save when not quoted or escaped.
- Output while in command line directory tree fails to
clearly show spaces when in such a directory.
3. Navigation from the command line.
- Without quoting or escaping the space at the beginning or
end of the file or directory name, you may end up in an
undesired location.
- Allows for duplicate directory naming. For example,
"python stuff" and "python stuff " or " python stuff".
while this could easily be blamed on the user, it could
also be prevented from happening.
What problem is it causing you?
I currently have an nfs share, a samba share, and an sshfs
share all connected to my Kubuntu machine. When trying to
transfer documents, it throws an error because the intened
destination was unable to be found (due to the space). While
it is easily fixed by removing the space, it could have been
avoided in the first place by stripping the leading/trailing
white spaces from the name of the file or directory.
Also, my son and wife use this computer, and tend to
inadvertently leave a trailing space after the name. Which
causes frustration for them.
(In reply to Nate Graham from comment #1)
> ...Bug reports that just describe a problem are usually more helpful than
> ones that propose a solution without explaining the problem.
I agree that fully understanding what is happening is helpful
for debugging. Having dealt with many bugs, myself, I also try
to prevent detail overloads. Hope this helps clarify what I
am experiencing.
--
You are receiving this mail because:
You are watching all bug changes.
