Hmm, you've got me thinking more now - maybe leave the command-line until
later. I certainly don't want to scare them off in the first chapter. I'm
so used to installing packages via raco I didn't even think of using
DrRacket.
On Sunday, April 1, 2018 at 7:18:33 PM UTC-4, HiPhish wrote:
>
> I d
You've gone above my pay-grade. :-)
On Sunday, April 1, 2018 at 1:05:17 PM UTC-4, Geoffrey Knauth wrote:
>
> On Sunday, April 1, 2018 at 12:57:46 PM UTC-4, Stephen Smith wrote:
>>
>> It's been a long tough road as to which implementation language to choose
>> for it. I'm down to two now after muc
I don't know where you are going with your book, but are you sure forcing
people to use the command-line interface is a good idea? Racket can be
fully used through the GUI (even managing packages can be done through
DrRacket). I agree with explaining both DrRacket and raco, but why can't
users
On Sunday, April 1, 2018 at 12:57:46 PM UTC-4, Stephen Smith wrote:
>
> It's been a long tough road as to which implementation language to choose
> for it. I'm down to two now after much experimenting - Racket of course,
> and Smalltalk.
>
Now you have me wondering which is harder, implementing
Lots of good advice and opinions here. Thanks everyone. I'll try to respond
to all of them in some way ...
1. @David K. Storrs and @Eric Eide: Renaming the folder. This works for
sure but _my_ preference is to use a symlink (as Eric also mentioned) as it
doesn't touch the original folder layout
Very interesting, good to know when I'm writing my own scripts, vs. using
things others have written. Thanks.
On Saturday, March 31, 2018 at 6:58:04 AM UTC-4, HiPhish wrote:
>
> BTW, on the topic of writing robust shell scripts, I always have a linter
> run over my scripts when I save them. I r
I understand the argument that strengthening our own CLI and shell-script
practice to guard against spaces in filenames is both learned and good
defense, as in, "don't go into battle without some armor protection." I do
that when I'm really worried, and if you want to see how big shell scripts
BTW, on the topic of writing robust shell scripts, I always have a linter
run over my scripts when I save them. I run Shellcheck automatically in
Neovim using the Neomake plugin. The linter catches among other things
missing quotations.
https://www.shellcheck.net/
https://github.com/neomake/neo
On Thursday, March 29, 2018 at 12:51:07 PM UTC-7, Stephen Smith wrote:
>
> Authoring a new Racket book (targeting all platforms and non-programmers)
>
>
Great idea! Are there more details you can share about the project?
--
You received this message because you are subscribed to the Google Grou
The benefit is that it looks nicer on the eyes in a GUI. I presume OP is
talking about the Racket installation you get off the Racket website, and
that installation is targeted at GUI users. I myself prefer the
command-line and I use Racket via Homebrew, so I never even come across
this issue.
On Thu, Mar 29, 2018 at 5:54 PM, HiPhish 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
Count me in as a person who renames racket installations without spaces.
It is more prudent to design file names without special characters,
escapes, or quotes. Otherwise, any shell script that might otherwise work
on most unix file names may fail. It's just not worth the hassle guessing
if a
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 lik
David Storrs writes:
> Second the desire for this not to be the case. Personally, my
> solution is just to rename the folder after installing it. I am
> currently working with binaries from
> /Applications/Racket_v6.11/bin/...
FWIW, I make a symlink (with no spaces in the name) and always use
14 matches
Mail list logo