There's also another issue.
Long filenames, and allowing spaces in filenames, are primarily
creatures of the GUI. They work great in Mac OS, and WinDoze, and in the
Gnome and KDE GUIs for Linux, but not so great if you have to open up a
command line in any of those operating systems. If you have a long name
in an OS that is used primarily from a command line, you increase the
amount of typing involved (and the possibility that a typo might cause
some real grief), and if you need command-line access to something with
embedded spaces in the name, it needs to be quoted. I'm sure that most
of us have gotten a taste of that just from long (and space-embedded)
names in the IFS.
--
JHHL
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
