New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move "Why Isn't it Doing Anything?" to an earlier episode #836

Open
Bioscibrarian opened this Issue Aug 21, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@Bioscibrarian

Bioscibrarian commented Aug 21, 2018

The note "Why Isn't it Doing Anything?" is introduced in Episode 6.
It describes how a command will wait for input if the user forgets to add a filename for a command to take action on.

The command used for an example is part of a piped setof commands. It is wc -l, without a filename given, so wc is waiting for input.

I think that shell novices might make this mistake earlier in the class--I know I did when I first learned bash commands.

It is possible to introduce "Why Isn't it Doing Anything?" as early as Episode 4 (Pipes and Filters):

  • The text in the lesson is:
    If we run wc -l instead of just wc, the output shows only the number of lines per file:
    $ wc -l *.pdb

  • Could we introduce "Why Isn't it Doing Anything?" here, and describe what would happen if the user just typed "wc -l" (without *.pdb)?

  • Then it might be useful to introduce Ctrl-Z or some other command-suspending intervention. I know this might be too much to introduce, but I have been a helper in sessions when at least one or two people have gotten "stuck" in a bash command that was waiting for input. Students need to know at some point how to suspend a command.

This is part of my Instructor Training Checkout, but it's also something I would like to see introduced a bit earlier in the lessons. -Thanks!
Pamela Shaw, Northwestern University

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment