The Makefile I use with JavaScript projects

Re:The Makefile I use with JavaScript projects by ratboy666 on Wednesday February 28, 2018 @04:52PM (#16487424)

Um... no it doesn't. It takes each space delimited name as a new name. You will need to add "" and quote the names -- but Windows shell only has one level of quoting, (") which means you can't easily type the command you need. Unix shell is a bit better. Unix only appears worse because people do attempt scripting.

Directory of C:\Users\fred

12/14/2017 04:44 PM 1,556 new 2.txt 1 File(s) 1,556 bytes 0 Dir(s) 75,989,876,736 bytes free

C:\Users\fred>dir new 2.txt Volume in drive C has no label. Volume Serial Number is BA05-C445

Directory of C:\Users\fred

File Not Found

C:\Users\fred>

[ Parent | on HN ]

Re:The Makefile I use with JavaScript projects by com2kid on Wednesday February 28, 2018 @08:04PM (#16488824)

> Um... no it doesn't. It takes each space delimited name as a new name. You will need to add "" and quote the names -- but Windows shell only has one level of quoting, (") which means you can't easily type the command you need. Unix shell is a bit better. Unix only appears worse because people do attempt scripting.

Ah I see, you have a file "new 2.txt", I was a bit confused.

Not sure what you mean by only 1 level of quoting being a problem, sorry.

[ Parent | on HN ]

Re:The Makefile I use with JavaScript projects by grive on Thursday March 01, 2018 @07:13AM (#16491368)

> Ah I see, you have a file "new 2.txt", I was a bit confused.

This is highly ironical, given this thread.

Some people seems to advocate for programs to be better than humans at globbing filenames.

[ Parent | on HN ]

Re:The Makefile I use with JavaScript projects by jstimpfle on Thursday March 01, 2018 @08:00AM (#16491562)

That's a great point. Computers sure have the potential to deal with spaces just fine. But if textual interaction is a requirement, we can only have one of arbitrary filenames and clutter-free syntax.

[ Parent | on HN ]