On Thu, Mar 29, 2018 at 5:54 PM, HiPhish <hiph...@openmailbox.org> wrote: > I think you are trying to solve the wrong problem. If people want to use a > command-line tool they should know how to use the command line first. They > don't have to know every arcane feature of the Bourne Shell, but knowing to > escape spaces or quote strings is the bare minimum. Think about it like > this: if you are trying to give someone directions you already assume they > know how to drive a car, right? If you want to write a book on Racket, then > focus on Racket. And if they cannot use the command-line they can still use > the GUI tools. >
I look at it the other way: there are clear benefits to NOT having names containing characters that need to be quoted, so any use of such characters has an opportunity cost. What benefit does the space provide that outweighs that opportunity cost? > On Thursday, March 29, 2018 at 9:51:07 PM UTC+2, Stephen Smith wrote: >> >> Authoring a new Racket book (targeting all platforms and non-programmers) >> and having to tell users to quote paths with spaces to be able to use the >> command-line tools seems distracting and an unnecessary complexity to impose >> on them. > > -- > You received this message because you are subscribed to the Google Groups > "Racket Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to racket-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
