I guess I'd need to see an example of how these characters trip someone
up in a file name using a BASH script while they are handled differently
in the DOS batch processor. With few exceptions, I find quoting literals
to work both in a script file and on the command line.
On 07/29/2015 09:11 AM, Janina Sajka wrote:
It's awkward because it often doesn't stop at spaces. It often also
involves commas, parenthesis, and similar reserved chars.
Christopher Chaltain writes:
How is dealing with file names with blanks in them awkward? I put those file
names in quotes, just like I do in Windows and other operating systems.
Maybe DOS and the old 8.3 file names didn't support spaces in them, but I
would hardly consider this to be an advantage of DOS over Linux.
On 07/29/2015 12:50 AM, Willem van der Walt wrote:
Hi,
You said:
for example, dealing with filenames
that contain spaces is awkward.
One of the best things about unix, is that some one else likely had the
same problem as what you are having now.
There is likely a tool written to solve exactly one's problem.
In the case of spaces in file names as well as other characters that can
cause problems, the tool is called detox.
It, for example, changes the & character into the word and.
People using GUIs invariably create those sentences for file names,
punctuation and all!
Regards, Willem
On Tue, 28 Jul 2015, Joel Roth wrote:
Janina Sajka wrote:
I love scripting. It's fun, and it solves problems for me.
There is a version of Linux, GoboLinux, with major utilities written
as shell scripts.
**And** there are some well-known limitations and
infelicities in bash, for example, dealing with filenames
that contain spaces is awkward.
Joel
Janina
--
Joel Roth
_______________________________________________
Blinux-list mailing list
Blinux-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/blinux-list
--
This message is subject to the CSIR's copyright terms and conditions,
e-mail legal notice, and implemented Open Document Format (ODF) standard.
The full disclaimer details can be found at
http://www.csir.co.za/disclaimer.html.
This message has been scanned for viruses and dangerous content by
MailScanner,
and is believed to be clean.
Please consider the environment before printing this email.
_______________________________________________
Blinux-list mailing list
Blinux-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/blinux-list
--
Christopher (CJ)
chaltain at Gmail
_______________________________________________
Blinux-list mailing list
Blinux-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/blinux-list
--
Christopher (CJ)
chaltain at Gmail
_______________________________________________
Blinux-list mailing list
Blinux-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/blinux-list